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

Untested: Have Autorevision create a PR instead of trying to push #1046

Merged
merged 2 commits into from
Jun 25, 2022

Conversation

lmoureaux
Copy link
Contributor

Direct pushes to master are forbidden by branch protection rules. Have the
automation create a PR instead, so we can approve it and enable automerge. It's
a bit less convenient than a push but good enough for now. It also lets us
check that the action is working is intended. If this works well, we could
consider enabling automerge from within the action (or pushing directly as it
looks like it's supported via an access token [1]).

Closes #955.

[1] stefanzweifel/git-auto-commit-action#87

Direct pushes to master are forbidden by branch protection rules. Have the
automation create a PR instead, so we can approve it and enable automerge. It's
a bit less convenient than a push but good enough for now. It also lets us
check that the action is working is intended. If this works well, we could
consider enabling automerge from within the action (or pushing directly as it
looks like it's supported via an access token [1]).

Closes longturn#955.

[1] stefanzweifel/git-auto-commit-action#87
@lmoureaux lmoureaux requested a review from jwrober June 25, 2022 15:52
@lmoureaux lmoureaux marked this pull request as ready for review June 25, 2022 15:52
@jwrober
Copy link
Collaborator

jwrober commented Jun 25, 2022

Does this mean that when we tag a release, the whole release process is paused until we approve of the PR and then once approved all the rest of the release process will continue including making the .zip, .gz archives and the varying binary packages for Windows, Debian and MacOS?

@lmoureaux
Copy link
Contributor Author

Does this mean that when we tag a release, the whole release process is paused until we approve of the PR and then once approved all the rest of the release process will continue including making the .zip, .gz archives and the varying binary packages for Windows, Debian and MacOS?

Source archive creation is not paused. I guess we should also run the autorevision updater before creating the tarball? Binary packages rely on the git version of autorevision.

Don't rely one someone else having done it earlier, since the file only gets
updated when the PR is merged.

See longturn#1046.
@lmoureaux lmoureaux enabled auto-merge (rebase) June 25, 2022 23:30
@lmoureaux lmoureaux merged commit c9f52f0 into longturn:master Jun 25, 2022
@lmoureaux lmoureaux deleted the bugfix/autorevision branch June 25, 2022 23:36
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.

AutoRevision.txt CI update fails at release time
2 participants