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

[chore] Create GitHub releases in addition to tags #3543

Closed
amis92 opened this issue Jul 23, 2020 · 3 comments
Closed

[chore] Create GitHub releases in addition to tags #3543

amis92 opened this issue Jul 23, 2020 · 3 comments
Labels
area:dev-ops Pertains to build, CI, and other dev-ops work community:request Issues specifically reported by a member of the community. improvement A non-feature-adding improvement status:in-progress Work is in progress

Comments

@amis92
Copy link

amis92 commented Jul 23, 2020

What feature are you requesting?
In addition to creating tags, please create full GitHub releases as well.

What would be the benefit of adding this feature?
People who watch releases on this repository would be notified.

What solution would be ideal for you?
Creating a GitHub release for new package tags, e.g. for 1.6.0 version of all packages create a single 1.6.0 release to notify watchers about it.

What alternatives have you considered?
None really, just ignore this request.

Is there any additional context for your request?
Currently 55 people are watching, hard to say how many watch just releases - I know I am.

PS Love this, but honestly I think not enough coverage in MSFT media was given on this project. I've randomly stumbled on it a couple of days ago in one of .NET Community Standup streams.

While Beachball doesn't natively integrate with Github releases, the Fluent UI team has created some scripts to facilitate this integration. That implementation could be leveraged in part or in whole to replicate the functionality.

Note GitHub Releases may be going through some future changes so putting this near the end of the backlog.

@amis92 amis92 added the status:triage New Issue - needs triage label Jul 23, 2020
@chrisdholt chrisdholt added area:dev-ops Pertains to build, CI, and other dev-ops work improvement A non-feature-adding improvement and removed status:triage New Issue - needs triage labels Jul 23, 2020
@chrisdholt
Copy link
Member

Thanks for the issue @amis92! We've definitely discussed this as we look into how we manage and deploy our packages. While we have some larger long-term goals for updating our release process, there may be some incremental steps we can take to get this out the door sooner.

In terms of your note on coverage, we've only recently started speaking externally and we're glad you found us! I think the work to move the MSFT implementation to Fluent UI with #3542 will likely lead to a bit more of the coverage you mention :).

@EisenbergEffect EisenbergEffect added the community:request Issues specifically reported by a member of the community. label Jul 24, 2020
@awentzel awentzel added the status:in-progress Work is in progress label Oct 10, 2020
@awentzel awentzel self-assigned this Oct 10, 2020
@awentzel awentzel removed their assignment Nov 16, 2020
@awentzel
Copy link
Collaborator

awentzel commented Jan 4, 2021

This works depends on #3889 and it's dependencies.

@awentzel
Copy link
Collaborator

This work is now completed and GitHub Releases should be updated nightly or as needed depending on what changes are being made each day. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:dev-ops Pertains to build, CI, and other dev-ops work community:request Issues specifically reported by a member of the community. improvement A non-feature-adding improvement status:in-progress Work is in progress
Projects
None yet
Development

No branches or pull requests

4 participants