-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
CI: Add bot to track deprecation prs #51723
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is really cool. I guess a bit of manual intervention may still be needed sometimes, but amazing automation.
i don't know enough about GH workflows to comment on the implementation, but the idea sounds really neat |
+1 for trying this out. |
Nice, on board with the idea I'm no security expert, but I guess there's no way for this to be exploited to get the secrets out of it? |
I don’t think so, I am basically using the same technique as our assign bot. Also, it’s not possible to trigger the bot again after the pr is merged |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, happy to trust you on this one
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
I'll merge this, we can always revert if we get any problems. I have a deprecation pr ready that can test the bot |
env: | ||
DEPRECATION_TRACKER_ISSUE: 50578 | ||
steps: | ||
- name: Checkout |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NBD: But probably good to rename this like Add deprecation log
We tend to forget to register deprecation prs in our deprecation log. This bot aims to solve this. Every time a PR with the label Deprecate is merged, it adds a new entry to the deprecation log.
In a future version I'd like to add the option to also check enforced deprecations automatically.
One TODO is how to handle PRs where we enforce deprecations:
We could get race conditions in theory, but it is not very likely, so would address if it becomes a problem.
Tried this in my repo and worked reliably
Pinging everyone who is regularly merging prs, hope I did not forget anyone