MeeseeksDev
MeeseeksDev copied to clipboard
Development deployment of MeeseeksBox (use at your own risk)
Hi @Carreau We're trying to set up MeeseeksDev to use it for automatic backporting in scvi-tools. The issue I'm running into is that the bot keeps complaining about the target...
See e.g. https://github.com/scikit-image/scikit-image/pull/5243#issuecomment-809031809 I must admit I don't know how to look at the relevant logs. 😂
Trying to cherry-pick a squash-merge results in errors like: ``` ct 29 18:13:42 meeseeksbot app/web.1: ---------------------------------------- Oct 29 18:13:42 meeseeksbot app/web.1: == Cleaning up previsous work... Oct 29 18:13:42 meeseeksbot...
git rebase -x "black --fast . && git commit -a --amend --no-edit" --strategy-option=theirs --autosquash HEAD~3
When backporting a PR, it would be nice to acknowledge the original PR author as co-author of the backported commit (eg in pandas, we use the git log automatically to...
The scikit-learn devs use a nifty chrome extension to create a link to the documentation for a project built with CircleCI. Perhaps this is something that meeseeks could handle. Circle...
When backporting the bot attempt to reuse previous clone and just do a pull. This can fail, and then erase the full-repository and re-clone. One of the case where this...
Write a better error message instead of "something went wrong".
Catch all errror and also in particular check if the branch name to backport to exists.
@choldgraf and @tacaswell, about auto backport: What about a mini-language in milestone description, something in the milestone description(editable on GitHub) that tell the bots which branches to backport to; Something...