github-starred/conventionalcommits.org
2
0
Fork 0
mirror of https://github.com/conventional-commits/conventionalcommits.org.git synced 2026-05-23 06:10:51 -05:00
Code Issues 1.7k Packages Projects Releases Wiki Activity

[GH-ISSUE #22] Rename scope #669

New Issue
Closed
opened 2026-04-11 07:02:51 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-11 07:02:51 -05:00
Owner
Copy Link

Originally created by @goodmind on GitHub (Nov 5, 2017).
Original GitHub issue: https://github.com/conventional-commits/conventionalcommits.org/issues/22

What commit message should be if I rename/move file into other scope?

Originally created by @goodmind on GitHub (Nov 5, 2017). Original GitHub issue: https://github.com/conventional-commits/conventionalcommits.org/issues/22 What commit message should be if I rename/move file into other scope?
GiteaMirror commented 2026-04-11 07:02:52 -05:00
Author
Owner
Copy Link

@stevemao commented on GitHub (Nov 5, 2017):

I think you can include 2 scopes EG:

refactor(scope1,scope2): rename
<!-- gh-comment-id:342013825 --> @stevemao commented on GitHub (Nov 5, 2017): I think you can include 2 scopes EG: ``` refactor(scope1,scope2): rename ```
GiteaMirror commented 2026-04-11 07:02:53 -05:00
Author
Owner
Copy Link

@goodmind commented on GitHub (Nov 6, 2017):

Well, commitizen can't do something like this :(

<!-- gh-comment-id:342017593 --> @goodmind commented on GitHub (Nov 6, 2017): Well, commitizen can't do something like this :(
GiteaMirror commented 2026-04-11 07:02:53 -05:00
Author
Owner
Copy Link

@stevemao commented on GitHub (Nov 6, 2017):

I think you just need to type scope1,scope2 as your scope

<!-- gh-comment-id:342036802 --> @stevemao commented on GitHub (Nov 6, 2017): I think you just need to type `scope1,scope2` as your scope
GiteaMirror commented 2026-04-11 07:02:54 -05:00
Author
Owner
Copy Link

@damianopetrungaro commented on GitHub (May 2, 2018):

Closing this one as solved :)

<!-- gh-comment-id:386131548 --> @damianopetrungaro commented on GitHub (May 2, 2018): Closing this one as solved :)
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#669
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?