MeeseeksDev
MeeseeksDev copied to clipboard
MeeseeksBox
Development deployment of MeeseeksBox (use at your own risk)
Hello and thanks for this very useful bot. We have a workflow where we forward-port change log from a release branch back to `main` at release time. Hence, we created...
I wonder if backporting instructions would be more helpful if instead of: ```bash git checkout 3.6.x git pull git cherry-pick -x -m1 1728207ffbad5baea1e77e4005230632bf6f16a6 git commit -am 'Backport PR #15279: Update...
One issue we have a lot is that merged PRs are assigned to the wrong milestones. For example, a PR was originally assigned to a milestone, then merged earlier or...
I think that would be helpful for visibility, and also I believe the bot does a bunch of things that are under the purview of scientific-python grant. I think that...
I made kind of a mess in #25034, partly cause i didn't quite grok which branch older branch is supposed to refer to here https://github.com/MeeseeksBox/MeeseeksDev/blob/46fe439f28c406e90a7bb863b21ce3020eab3b20/meeseeksdev/meeseeksbox/commands.py#L895 and cherry picked into v3.7.x...
Currently can't backport this PR (https://github.com/scverse/scvi-tools/pull/1490) Is there a way I can view the logs? Thanks!
There was some issues with heroku recently. Bot needs to be redeployed manually this is a test issue.
One of the goal for mr meeseeks is to _not_ have write permission to repositories for security reason as most actions are done via the meeseeksmachine user though it currently...
When we use the meeseeksdev command, it points to an actual account: https://github.com/meeseeksdev So this person is getting notified every time we use a command? Or am I getting confused?
In Astropy we've been enjoying using MeeseeksDev. I use a project board to track and categorize my PRs, current and intended. When A PR in the project is backported using...
Metadata
Owner
Metadata
Development deployment of MeeseeksBox (use at your own risk)