-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
feat(supersetbot): introduce supersetbot
as its own npm package, CLI and comment-operated bot
#27046
Conversation
@supersetbot label preset-io |
7 similar comments
@supersetbot label preset-io |
@supersetbot label preset-io |
@supersetbot label preset-io |
@supersetbot label preset-io |
@supersetbot label preset-io |
@supersetbot label preset-io |
@supersetbot label preset-io |
test |
@supersetbot label preset-io |
1 similar comment
@supersetbot label preset-io |
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 awesome, #TIL
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.
Only one change request... this seems like it'd cause some potential release/security issue, if I'm not mistaken and anyone can remove any tag. We should probably have some means to protect important tags (or namespaces thereof) like release numbers that Cherry Tree uses, or hold
tags, for example.
a2d8034
to
84de22a
Compare
supersetbot
as its own npm package, CLI and comment-operated bot
7834771
to
4aa6149
Compare
1970e29
to
3d9d752
Compare
58102b1
to
712de13
Compare
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.
LGTM — I think the last thing it needs (which could be done separately) is adding some documentation. Either a page on the docs site, or maybe a page on the wiki. The description on the PR here is a great starting point — a tweaked version of that would suffice to raise initial awareness.
9d8826e
to
998f47d
Compare
…I and comment-operated bot (apache#27046)
…I and comment-operated bot (apache#27046)
…I and comment-operated bot (apache#27046)
SUMMARY
While GitHub actions are powerful, it's been hard to work with actions as they hard to develop, test, and debug.
Introducing a new
supsersetbot
utility bot that can be used to help around GitHub, CI and beyond. For now it does some basic things like labeling PRs and issues, but the idea is to grow it to serve set of utility functions to help around GitHub, GitHub actions, CI, release management and the repo int general. Things like managing ephemeral environments, supporting release management.Because it's a proper npm app, it can be tested, versioned, deployed and used locally.
It's a CLI as in:
But it can also be called from GitHub comments, as in:
This means that PR comments can be used a bit more like a terminal, and committers and users can trigger things. Note that it's fully context-aware, nows whether the commenter is a committer, and can decide who should be able to do what.
While this first version brings back the funcitonality we had with a previous, hosted now defunct
supersetbot
, the vision is to extend it to manage ephemeral envs, tag PRs with release-related information, ...