Skip to content
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.

Sign up for GitHub

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

Docs add info #1208

Merged
merged 4 commits into from
Jan 6, 2025
Merged

Docs add info #1208

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6849321
Update CONTRIBUTING.md
dbirman Jan 3, 2025
15b4676
bump schema version [skip actions]
github-actions[bot] Jan 3, 2025
c9e76e2
Revert "bump schema version [skip actions]"
dbirman Jan 6, 2025
ecd2579
chore: minor
dbirman Jan 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,4 +102,15 @@ where scope (optional) describes the packages affected by the code changes and t
- **test**: Adding missing tests or correcting existing tests
to set up your environment.

When you are ready to open a pull request, please link any relevant issues and request a review. Thanks for contributing!
When you are ready to open a pull request, please link any relevant issues and request a review. Thanks for contributing!

## Release

- From dev, create a branch called release-vX.Y.Z
- Manually increment the version number in the aind_data_schema/__init__.py file to match
- Manually increment the major/minor/patch versions of the core files as needed
- Push the branch and open a PR into main
- After this push, any last minute changes to the release-vX.Y.Z will have to done to via a PR
- After review, use a merge commit to merge into main
- Open a PR from main back into dev so they're synced again
- Create a Github release with the corresponding tag, modify the auto-generated release notes to focus on the major changes that occurred
Loading