Skip to content

ci: Add a workflow for creating releases#3804

Merged
straker merged 13 commits intodevelopfrom
release-workflow
Dec 6, 2022
Merged

ci: Add a workflow for creating releases#3804
straker merged 13 commits intodevelopfrom
release-workflow

Conversation

@stephenmathieson
Copy link
Copy Markdown
Member

@stephenmathieson stephenmathieson commented Nov 29, 2022

Example release PR: #3814

Ref https://github.com/dequelabs/axe-api-team/issues/304

<< Describe the changes >>

Closes issue:

@stephenmathieson stephenmathieson requested a review from a team as a code owner November 29, 2022 16:45
WilcoFiers
WilcoFiers previously approved these changes Dec 1, 2022
Copy link
Copy Markdown
Contributor

@WilcoFiers WilcoFiers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I would like @straker's review of this too before we merge.

@stephenmathieson
Copy link
Copy Markdown
Member Author

I want to test this manually before merging. Haven't had the time to do so yet, but will soon.

straker
straker previously requested changes Dec 5, 2022
npm ci
npm run release

git push origin "$Branch" --force
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why the force push?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the branch already has changes in it, we'll want to overwrite them.

Copy link
Copy Markdown
Contributor

@straker straker Dec 5, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't the checkout action fail then and kill the build before it got to this point? Not that it's preventing the pr from going through, was just curious

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, the checkout action is taking whatever branch we're releasing from (usually develop). We then create this branch, add the release commit, then push. The --force is to ensure any prior pending release (maybe someone made a mistake) is overwritten.

This is, however, fixing a problem we haven't had (yet?). I'm happy to pull it out if you aren't comfortable force pushing.

Copy link
Copy Markdown
Contributor

@straker straker Dec 5, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wilco didn't seem to think it was a problem when he reviewed it, so I'm fine with it.

edit: actually turns out wilcos review did not cover this line. let me confirm with him first before merging

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see how it matters. If the branch already exists checkout -b will fail. I'm good with it as-is.

stephenmathieson and others added 2 commits December 5, 2022 13:28
Co-authored-by: Steven Lambert <2433219+straker@users.noreply.github.com>
Co-authored-by: Steven Lambert <2433219+straker@users.noreply.github.com>
npm ci
npm run release

git push origin "$Branch" --force
Copy link
Copy Markdown
Contributor

@straker straker Dec 5, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wilco didn't seem to think it was a problem when he reviewed it, so I'm fine with it.

edit: actually turns out wilcos review did not cover this line. let me confirm with him first before merging

npm ci
npm run release

git push origin "$Branch" --force
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see how it matters. If the branch already exists checkout -b will fail. I'm good with it as-is.

@straker straker merged commit 6d01604 into develop Dec 6, 2022
@straker straker deleted the release-workflow branch December 6, 2022 15:07
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 this pull request may close these issues.

3 participants