search

masa-finance / masa-bittensor

Bittensor Subnet Config
https://masa.ai
MIT License
0 stars 0 forks source link

ci(release): add release configuration #131

Closed mudler closed 2 days ago

mudler commented 2 days ago

Closes #83 .

It adds the configuration for github automated release notes generation from the labels in the PRs

juanmanso commented 2 days ago

Relates to #83 .

It adds the configuration for github automated release notes generation from the labels in the PRs

Also doesn't this PR close #83?

mudler commented 2 days ago

Relates to #83 . It adds the configuration for github automated release notes generation from the labels in the PRs

Also doesn't this PR close #83?

potentially - I'm not sure of the issue wanted outcome. This allows to hit on the button "Generate automated release notes" which will generate autoamtically the changelogs when creating a release on github. so it is "partially" automated at this point

juanmanso commented 2 days ago

Relates to #83 . It adds the configuration for github automated release notes generation from the labels in the PRs

Also doesn't this PR close #83?

potentially - I'm not sure of the issue wanted outcome. This allows to hit on the button "Generate automated release notes" which will generate autoamtically the changelogs when creating a release on github. so it is "partially" automated at this point

Personally, I think this closes the task since it automates the generation but it's triggered on demand. Another kind of automation is to trigger that based on a tag, however it still needs some trigger. Thus, I think this suffices to close #83.

Either way, since release checklist is a bit rough still, this automation is a good enough implementation for our first couple of releases (if we see that releases are too fast too often, we should come back to it IMO)

mudler commented 2 days ago

Relates to #83 . It adds the configuration for github automated release notes generation from the labels in the PRs

Also doesn't this PR close #83?

potentially - I'm not sure of the issue wanted outcome. This allows to hit on the button "Generate automated release notes" which will generate autoamtically the changelogs when creating a release on github. so it is "partially" automated at this point

Personally, I think this closes the task since it automates the generation but it's triggered on demand. Another kind of automation is to trigger that based on a tag, however it still needs some trigger. Thus, I think this suffices to close #83.

Either way, since release checklist is a bit rough still, this automation is a good enough implementation for our first couple of releases (if we see that releases are too fast too often, we should come back to it IMO)

sounds good here :+1: