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.

Sign up for GitHub

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

Jump to bottom

Ensure that only fully-tested commits can be pushed & only tagged revs can be published #135

Closed
luczsoma opened this issue Oct 20, 2019 · 0 comments · Fixed by #136
Closed

Ensure that only fully-tested commits can be pushed & only tagged revs can be published #135

luczsoma opened this issue Oct 20, 2019 · 0 comments · Fixed by #136
Assignees
@luczsoma

Comments

@luczsoma
Copy link
Member

No description provided.

@luczsoma luczsoma self-assigned this Oct 20, 2019
luczsoma added a commit that referenced this issue Oct 20, 2019
@luczsoma
ci: Ensure only fully tested pushes and only correctly tagged releases
7da2354 
On git push, everything is tested. On npm publish, the package version
is matched with the released revision's tag to avoid accidental
releases.

Closes #135.
@luczsoma luczsoma mentioned this issue Oct 20, 2019
Merged
16 tasks
luczsoma added a commit that referenced this issue Oct 20, 2019
@luczsoma
ci: Ensure only fully tested pushes and only correctly tagged releases
3ca3e4a 
On git push, everything is tested. On npm publish, the package version
is matched with the released revision's tag to avoid accidental
releases.

Closes #135.
luczsoma added a commit that referenced this issue Oct 20, 2019
@luczsoma
ci: Ensure only fully tested pushes and only correctly tagged releases
0acf3de 
On git push, everything is tested. On npm publish, the package version
is matched with the released revision's tag to avoid accidental
releases.

Closes #135.
luczsoma added a commit that referenced this issue Feb 14, 2020
@luczsoma
ci: Ensure only fully tested pushes and only correctly tagged releases
647beb8 
On git push, everything is tested. On npm publish, the package version
is matched with the released revision's tag to avoid accidental
releases.

Closes #135.
luczsoma added a commit that referenced this issue Feb 14, 2020
@luczsoma
ci: Ensure only fully tested pushes and only correctly tagged releases
ca517fc 
On git push, everything is tested. On npm publish, the package version
is matched with the released revision's tag to avoid accidental
releases.

Closes #135.
luczsoma added a commit that referenced this issue Mar 28, 2021
@luczsoma
ci: Ensure only fully tested pushes and only correctly tagged releases
45b24d3 
On git push, everything is tested. On npm publish, the package version
is matched with the released revision's tag to avoid accidental
releases.

Closes #135.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@luczsoma luczsoma

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

ci: Ensure only fully tested pushes and only correctly tagged releases Diplomatiq/crypto-random
1 participant
@luczsoma