-
-
Notifications
You must be signed in to change notification settings - Fork 409
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
Enable automerge on pre and post-release workflows #2010
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
epassaro
force-pushed
the
ci/enable-automerge
branch
from
May 4, 2022 20:42
db7d4bf
to
ee89b5c
Compare
Codecov Report
@@ Coverage Diff @@
## master #2010 +/- ##
=======================================
Coverage 59.87% 59.87%
=======================================
Files 70 70
Lines 8157 8157
=======================================
Hits 4884 4884
Misses 3273 3273 📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
epassaro
force-pushed
the
ci/enable-automerge
branch
from
May 4, 2022 21:20
6a5228f
to
dce47c7
Compare
epassaro
force-pushed
the
ci/enable-automerge
branch
2 times, most recently
from
May 5, 2022 22:44
7290f18
to
267d441
Compare
epassaro
force-pushed
the
ci/enable-automerge
branch
from
May 7, 2022 21:17
3888117
to
cb9a242
Compare
*beep* *bop* Hi, human. The Click here to see the build log. |
epassaro
force-pushed
the
ci/enable-automerge
branch
from
May 7, 2022 22:50
7c233b9
to
cb9a242
Compare
epassaro
changed the title
Enable automerge on pre and post-release workflows
Prepare automerge on pre and post-release workflows
May 8, 2022
epassaro
force-pushed
the
ci/enable-automerge
branch
3 times, most recently
from
May 8, 2022 22:39
4255814
to
8228180
Compare
epassaro
force-pushed
the
ci/enable-automerge
branch
3 times, most recently
from
May 31, 2022 16:24
82fd7fa
to
c756f32
Compare
epassaro
force-pushed
the
ci/enable-automerge
branch
from
May 31, 2022 18:32
55e96c0
to
9062801
Compare
epassaro
force-pushed
the
ci/enable-automerge
branch
from
May 31, 2022 19:10
653deae
to
b7a1a0c
Compare
epassaro
changed the title
Prepare automerge on pre and post-release workflows
Enable automerge on pre and post-release workflows
May 31, 2022
epassaro
requested review from
andrewfullard and
wkerzendorf
and removed request for
tardis-bot
May 31, 2022 19:39
Seems sensible, assuming we set the bot up correctly. |
epassaro
force-pushed
the
ci/enable-automerge
branch
from
June 2, 2022 18:09
862c6ce
to
4574a52
Compare
epassaro
force-pushed
the
ci/enable-automerge
branch
from
June 5, 2022 18:40
4574a52
to
dbf904b
Compare
Rodot-
approved these changes
Jun 6, 2022
andrewfullard
approved these changes
Jun 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Automerge requires important changes in the TARDIS infrastructure:
Add branch protection rules to enforce passingDONEtests
anddocs
before merging a pull requestMake @tardis-bot a less privileged user to avoid merging pull requests with failing tests. In this moment the bot has administator rights and does not follow the principle of least privilege. All the operations made by the bot can be performed with less privileges (see this table)DONEThis pull request makes minor changes to
pre
andpost
release:Other changes:
docs
workflow (required to mark this job as a required status check before automerge).Motivation and context
How has this been tested?
Examples
Type of change
Checklist
build_docs
label to this pull request (if you don't have enough privileges a reviewer will do it for you)