github-starred/conventionalcommits.org
2
0
Fork 0
mirror of https://github.com/conventional-commits/conventionalcommits.org.git synced 2026-03-22 21:24:02 -05:00
Code Issues 153 Packages Projects Releases Wiki Activity

Guidance for a security type #121

New Issue
Closed
opened 2026-02-17 11:47:59 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-02-17 11:47:59 -06:00
Owner
Copy Link

Originally created by @feanil on GitHub (Feb 25, 2021).

While adopting this spec one thing that stood out was the lack of a security type in the standard. Is there a best practice for this? Or would the committee be open to adding some guidance around how to manage security fixes?

Originally created by @feanil on GitHub (Feb 25, 2021). While adopting this spec one thing that stood out was the lack of a `security` type in the standard. Is there a best practice for this? Or would the committee be open to adding some guidance around how to manage security fixes?
GiteaMirror commented 2026-02-17 11:48:01 -06:00
Author
Owner
Copy Link

@damianopetrungaro commented on GitHub (Mar 8, 2021):

@feanil the only "standard type" are feat or fix, you can add as many custom types as you want in your own project :)

@damianopetrungaro commented on GitHub (Mar 8, 2021): @feanil the only "standard type" are feat or fix, you can add as many custom types as you want in your own project :)
GiteaMirror commented 2026-02-17 11:48:02 -06:00
Author
Owner
Copy Link

@damianopetrungaro commented on GitHub (Mar 8, 2021):

Gonna close it, if you still have questions or doubts please let me know!

@damianopetrungaro commented on GitHub (Mar 8, 2021): Gonna close it, if you still have questions or doubts please let me know!
GiteaMirror commented 2026-02-17 11:48:04 -06:00
Author
Owner
Copy Link

@d-damien commented on GitHub (Jan 15, 2023):

I'm about to start using as I think it deserves its own type indeed, given the importance of security in CS. Seeing as other types are all short − perf, doc etc. − I'll take sec.

@d-damien commented on GitHub (Jan 15, 2023): I'm about to start using as I think it deserves its own type indeed, given the importance of security in CS. Seeing as other types are all short − perf, doc etc. − I'll take `sec`.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
discussion
enhancement
greenkeeper
help wanted
meeting-agenda
operations
process
pull-request
Mirrored from GitHub Pull Request
 question
suggestion
support
triaged
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/conventionalcommits.org#121
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?