adding readme badges and pyproject author #317
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tjhladish
approved these changes
Jan 14, 2025
|
@arik-shurygin re: branches for release process, I'm reviewing the "Release Process" part of the Predict handbook, and it sounds somewhat different from what you were implying. |
edbaskerville
approved these changes
Jan 14, 2025
I was unaware there was explicit guidance on this now here and here. We can get CHANGELOG to generate when deciding to go from main to |
|
@edbaskerville do you think we need both of these badges? Maybe just the right one is enough |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
a small commit meant to work on #314 but not closing that yet until we set up auto changelogs on release, badges will now display the package version which can be incremented by each PR into main.
I am going to assume that we will transition into a
staging-> productionformat where main will be reserved for each release and sets of PRs will be made into astagingbranch before going out as a release inmain. This has not been something we have been doing up to this point due to the early nature of the project.