mirror of
https://github.com/conventional-commits/conventionalcommits.org.git
synced 2026-03-22 12:44:37 -05:00
Criteria For Migrating conventional-changelog Projects #33
Reference in New Issue
Block a user
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?
Originally created by @hutson on GitHub (Aug 12, 2018).
What are the criteria for migrating
conventional-changelogprojects to the new organization?@damianopetrungaro commented on GitHub (Aug 12, 2018):
I think that there are no breaking changes after this rename because all the services that are using the linked repository will be redirected to the new one.
But anyway we should update the reference of the repository 😄
@hbetts feel free to add more of them, and @bcoe and @stevemao you may have more info because he was the main owner for a while 😄
@damianopetrungaro commented on GitHub (Aug 12, 2018):
@bcoe you are the only owner on the Heroku app, you should edit it 😛
@hutson commented on GitHub (Aug 19, 2018):
@damianopetrungaro I was actually looking for an answer to whether
conventional-changelogis a good candidate to move into this org? How do I know it's a good candidate for this org? Who needs to approve the repository to be moved into this org?@damianopetrungaro commented on GitHub (Aug 20, 2018):
dunno if moving
conventional-changelog/conventional-changelogintoconventional-commits/conventional-changelogis the best thing, one is related to commits and the other one to changelogs.My 2 cents are:
If sth is related about the commit message specs, we can put it here, for example:
https://github.com/commitizen/cz-conventional-changelog
or
https://github.com/damianopetrungaro/php-commitizen
@hutson commented on GitHub (Aug 22, 2018):
Sounds good @damianopetrungaro.
If we need to define this better, let's move it to our
metaproject.