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

🚀. Create patch workflow for Nuget Package #224

Open
1 task done
keithrfung opened this issue Oct 21, 2021 · 0 comments
Open
1 task done

🚀. Create patch workflow for Nuget Package #224

keithrfung opened this issue Oct 21, 2021 · 0 comments
Labels
enhancement New feature or request hacktoberfest Issues for the Hacktoberfest help wanted Extra attention is needed

Comments

@keithrfung
Copy link
Collaborator

Is there an existing issue for this?

  • I have searched the existing issues

Suggestion

Create a patch workflow for releasing the Nuget package into GitHub.
https://github.com/microsoft/electionguard-cpp/tree/main/.github/workflows

This workflow will create a patch nuget package to have a nuget package released immediately with quick changes on the GitHub registry. This patch workflow will not release a package on nuget.org.

Possible Implementation

  1. Create a new workflow labeled patch
    • Workflow should run after pull requests are merged
  2. Auto increment the semantic version by one patch number (See 🆙 Add a workflow to auto increment the version #222 )
  3. Build nuget package similar to release workflow
  4. Release nuget package on Github Package Registry (See 🚀. Publish to GitHub Nuget Registry in Release Workflow #223 )

Anything else?

No response

@keithrfung keithrfung added enhancement New feature or request help wanted Extra attention is needed hacktoberfest Issues for the Hacktoberfest labels Oct 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request hacktoberfest Issues for the Hacktoberfest help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant