-
Notifications
You must be signed in to change notification settings - Fork 86
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
Automate More Complete Release Process #228
base: master
Are you sure you want to change the base?
Conversation
All contributors have signed the CLA ✍️ ✅ |
I have read the CLA Document and I hereby sign the CLA |
recheck |
I tested the automatic release functionality in my forked repo and it works the same and manually creating a Release with generated release notes. |
recheck |
@EyalDelarea I'm not sure how to request reviewer(s) |
@eyalbe4 I'm not sure how to request reviewer(s) |
@RobiNino could you please review / add reviewers on my behalf? |
@sverdlov93 Are public users allowed to propose these types of changes? I don't think I've missed any steps in the contributing guidelines |
npm run format
for formatting the code before submitting the pull request.MAJOR version tag is available for reference but when referenced can result in unexpected changes in behaviors downstream. Adding Minor version tag to reference allows for more stable dynamic resolving of action's updates.
Current release process for this repository is to manually create GitHub Release, which triggers release workflow. Instead, just run the workflow with some input and let the rest work out automatically.