How to: Maintain several versions #2661
Conversation
✅ Deploy Preview for conda-forge-previews ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| Open your `conda-forge.yml` file and add these lines: | ||
|
|
||
| ```yaml | ||
| abi_migration_branches: # TODO |
There was a problem hiding this comment.
It this a TODO for the doc or meant literally?
h-vetinari
left a comment
h-vetinari
left a comment
There was a problem hiding this comment.
This LGTM, though I think we may want to call out the following behaviour that can be annoying/surprising:
Creating a branch off of an old commit and adding it to abi_migration_branches will almost certainly cause the bot to create a whole bunch of pointless migrator PRs against that new branch, because the logic for when to create such a migrator PR is very sensitive to even the most minor rerender changes, which will almost always trigger for old commits (i.e. stuff that hasn't been rerendered in a while).
I still think it would be good to avoid this by double-rerendering for the maintenance branches, see regro/cf-scripts#2500
|
Good to know. I'll add a quick note but perhaps we should focus on fixing that surprising behavior too. |
3 participants
PR Checklist:
docs/orcommunity/, you have added it to the sidebar in the corresponding_sidebar.jsonfileCloses Quansight-Labs/conda-ecosystem-sta-mgmt#63