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.

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

Notification when software gets new release #141

Open
cjsha opened this issue Oct 31, 2024 · 2 comments
Open

Notification when software gets new release #141

cjsha opened this issue Oct 31, 2024 · 2 comments
Assignees
Milestone

Comments

@cjsha
Copy link
Member

cjsha commented Oct 31, 2024

I don't think this could be automated because we might need to take additional actions like generating new .bonsai workflows for new operators. But it would be nice to get a notification (maybe an issue?) in the docs repo that tells us we need update the submodule pointer.

@cjsha cjsha added this to the Wishlist milestone Oct 31, 2024
@cjsha cjsha mentioned this issue Oct 31, 2024
@bparks13
Copy link
Member

There is a way, we can actually automate it from the main repo so that when a new release is tagged it generates an issue here (I think, I've never actually done that but I am pretty sure it is possible). That would be as close to automating the release as I would like to get, since I agree that there are new workflows that need to be created.

For testing purposes, we can always have a development branch in this repo that points to the most recent commits in the main repo so that we can develop and test the workflows / extra pages before we push a new release as well.

@cjsha
Copy link
Member Author

cjsha commented Oct 31, 2024

maybe we should have a branch in the bonsai-onix1 repo that gets autopopulated with the latest tags. Then the we have a check when merging to main that asks if the submodule points to the correct commit on that branch? or something like that. Idk about the exact implementation but I like the idea of having some sort of check when merging to main to make sure it's pointing to the correct commit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants