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

feature request: supporting multiple scopes #111

New Issue
Open
opened 2026-02-17 11:47:04 -06:00 by GiteaMirror · 8 comments
GiteaMirror commented 2026-02-17 11:47:04 -06:00
Owner
Copy Link

Originally created by @privatenumber on GitHub (Oct 9, 2020).

Feature request

Requesting the Conventional Commits spec to support multiple scopes. eg.:

type(scope1,scope2): message

Use case

Some features/fixes may at times require multiple packages to be changed and this approach allows all affected scopes to be listed.

Relevant issues

Originally created by @privatenumber on GitHub (Oct 9, 2020). ### Feature request Requesting the Conventional Commits spec to support multiple scopes. eg.: ``` type(scope1,scope2): message ``` ### Use case > Some features/fixes may at times require multiple packages to be changed and this approach allows all affected scopes to be listed. - [@virkt25](https://github.com/conventional-changelog/commitlint/issues/75#issuecomment-330553248) ### Relevant issues - https://github.com/conventional-changelog/commitlint/issues/75 - https://github.com/conventional-changelog/conventional-changelog/issues/232 - https://github.com/conventional-commits/conventionalcommits.org/issues/22 - I noticed in this old issue, that this syntax is suggested as a way to indicate scope migration. I think a different syntax can be developed for that and also be documented in the spec. Perhaps `type(scope1->scope2)` or `type(scope1>scope2)`
GiteaMirror added the meeting-agenda label 2026-02-17 11:47:04 -06:00
GiteaMirror commented 2026-02-17 11:47:06 -06:00
Author
Owner
Copy Link

@timoxley commented on GitHub (Mar 16, 2021):

image

@bcoe Was there a meeting about this? What was the outcome? It looks like support was added in action-semantic-pull-request but I don't see any mention of multiple scopes in the conventionalcommits spec.

@timoxley commented on GitHub (Mar 16, 2021): ![image](https://user-images.githubusercontent.com/43438/111351002-13f58180-8659-11eb-9513-5612b769e31c.png) @bcoe Was there a meeting about this? What was the outcome? It looks like support was added in `action-semantic-pull-request` but I don't see any mention of multiple scopes in the conventionalcommits spec.
GiteaMirror commented 2026-02-17 11:47:07 -06:00
Author
Owner
Copy Link

@LightAndLight commented on GitHub (Nov 12, 2021):

Bumping this. It looks like conventional-changelog has supported this for a while now, but it's not mentioned on conventional-commits.org.

@LightAndLight commented on GitHub (Nov 12, 2021): Bumping this. It looks like `conventional-changelog` has supported this for a while now, but it's not mentioned on conventional-commits.org.
GiteaMirror commented 2026-02-17 11:47:09 -06:00
Author
Owner
Copy Link

@damianopetrungaro commented on GitHub (Nov 13, 2021):

This one looks interesting to me, could address the situation where for a BC I want to update multiple packages at the same time.
@bcoe i think this one should be mentioned, any bad feeling regarding this?

@damianopetrungaro commented on GitHub (Nov 13, 2021): This one looks interesting to me, could address the situation where for a BC I want to update multiple packages at the same time. @bcoe i think this one should be mentioned, any bad feeling regarding this?
GiteaMirror commented 2026-02-17 11:47:10 -06:00
Author
Owner
Copy Link

@smarts commented on GitHub (Jul 27, 2022):

image

@bcoe Was there a meeting about this? What was the outcome? It looks like support was added in action-semantic-pull-request but I don't see any mention of multiple scopes in the conventionalcommits spec.

asking this again since no reply…

@smarts commented on GitHub (Jul 27, 2022): > ![image](https://user-images.githubusercontent.com/43438/111351002-13f58180-8659-11eb-9513-5612b769e31c.png) > > @bcoe Was there a meeting about this? What was the outcome? It looks like support was added in `action-semantic-pull-request` but I don't see any mention of multiple scopes in the conventionalcommits spec. asking this again since no reply…
GiteaMirror commented 2026-02-17 11:47:11 -06:00
Author
Owner
Copy Link

@damianopetrungaro commented on GitHub (Jul 27, 2022):

@bcoe I feel you may have more context than myself on this

@damianopetrungaro commented on GitHub (Jul 27, 2022): @bcoe I feel you may have more context than myself on this
GiteaMirror commented 2026-02-17 11:47:12 -06:00
Author
Owner
Copy Link

@tinesoft commented on GitHub (Aug 26, 2022):

Hi all,
Any update on this?
This could be a great addition, specially in #monorepo projects...

@tinesoft commented on GitHub (Aug 26, 2022): Hi all, Any update on this? This could be a great addition, specially in #monorepo projects...
GiteaMirror commented 2026-02-17 11:47:13 -06:00
Author
Owner
Copy Link

@damianopetrungaro commented on GitHub (Sep 7, 2022):

Pinging back @bcoe if he has any 2 cents about it

@damianopetrungaro commented on GitHub (Sep 7, 2022): Pinging back @bcoe if he has any 2 cents about it
GiteaMirror commented 2026-02-17 11:47:14 -06:00
Author
Owner
Copy Link

@enell commented on GitHub (May 14, 2024):

Has there been any decisions on this or is this request abandoned?

@enell commented on GitHub (May 14, 2024): Has there been any decisions on this or is this request abandoned?
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 meeting-agenda
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#111
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?