Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ds-gitflows-template set-up fails #21

Closed
padilla410 opened this issue Aug 22, 2022 · 0 comments · Fixed by #22
Closed

ds-gitflows-template set-up fails #21

padilla410 opened this issue Aug 22, 2022 · 0 comments · Fixed by #22
Assignees

Comments

@padilla410
Copy link
Collaborator

padilla410 commented Aug 22, 2022

Diagnosis

GitHub actions fails after cloning the template and having @lindsayplatt kick off the initial build by starring the cloned repo. Here are a few screenshots and a link to a failing build:

image

image

We also know that this repo worked as recently as 8/4 because Jesse successfully ran the gitflows training for two new hires.

We found a few red herrings:

I am noting them here because the lack of any calls to python -m pip install helped me find the culprit. This led me to dig into Peter Evans' create-issue-from-file repo because it is called multiple times from .github/workflows/setup.yml. He had two PRs merged 4 days ago, upgrading to v4.

Troubleshooting a solution

To troubleshoot this I cloned this repo, made my own template, and assigned myself as the github.actor, updated Issue 1, and then tried to kick-off a new repo. With the stated updates, this repo successfully builds Issue 1 and fails on Issue 2 which was the expected action.

I also verified that changing all references to from v2 to v4 will allow the build to successfully complete.

I am now going to submit a PR to this repo that updates all actions from peter-evans/create-issue-from-file@v2 to peter-evans/create-issue-from-file@v4

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant