-
Notifications
You must be signed in to change notification settings - Fork 36
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
Default branches of some repos are not correct #828
Comments
@madebr may you share your script? |
@SSE4 You can reproduce the output above by executing: You'll probably run into rate limiting so you'll need to pass your login data or a [personal access token] I run the script as following:
or
By adding the |
If you plan to mass update the default branches somehow, then please remember to put the testing branches as default going forward |
yeah, that's the plan - some projects still have stable as a default branch |
@Croyden |
@SSE4 |
testing should be default, as we have agreed previously |
Please be careful when updating Boost. The testing/1.70.0 are WIP. And likely should not be the default. |
@grafikrobot I don't think that there is any real danger in doing that 🤔 |
well, users might assume that default branch is something recommended and stable (which is not true for boost recipes), and might start to use this, so betta exclude em from script for now |
Most people are consuming the recipes from BIntray which only has stable releases, not GitHub. And when the branch name is literally |
I think @Croydon has a good point. The testing label should be enough to discourage most from trying to use them. So, sure, make them default :-) |
I've updated the output in the first comment. |
default branches were updated |
Is this script completely automated and how stable is it? If so, we can clone it and create a cronjob for it |
currently, it requires an interactive input to confirm actions, so it's not suitable for cron yet
in case like above, it's hard to automatically guess the valid default branch |
these are good questions. I don't think that we should delete branches for such a reason. In some repositories we also have a master version or similar, or sometimes the version schema changes... so until we come up with something clever, I suppose no automation for now |
totally agree |
Hey,
I ran a script to check the default branches of Bincrafters's conan repos with the versions available.
Some repos have an older version as their default branch (these should be fixed).
Some repos their branch names do not contain a version or do not contain a recipe at all (these should be added).
The script does not recognize the versions of some repos. (ignore these)
Paste of the output of the script:
The text was updated successfully, but these errors were encountered: