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

[PR #2] [MERGED] feat: use semver.org as a basis for conventionalcommits.org #237

New Issue
Closed
opened 2026-02-17 11:55:22 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-17 11:55:22 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/conventional-commits/conventionalcommits.org/pull/2
Author: @bcoe
Created: 4/3/2017
Status: ✅ Merged
Merged: 4/8/2017
Merged by: @bcoe

Base: master ← Head: conventional-commits-spec

📝 Commits (10+)

  • ba53297 feat: use semver.org as a basis for conventionalcommits.org
  • af3cfd3 chore: fix typo unlease -> unleash
  • 8402359 docs: add clarifications to FAQ (#6)
  • 1535443 chore: switch to using Jekyll plugins directly, rather than using github-pages (#7)
  • 69e0477 chore: another pass of edits
  • 3566644 chore: a couple more edits based on @stevemao's feedback
  • 8281112 docs: captitalize semver appropriately
  • 5dd9294 docs: fix typo
  • 877d8ec docs: reason's 5 and 6 were pretty close, I think we can drop one
  • 0d9c350 docs: rephrase one of the FAQ questions a bit

📊 Changes

50 files changed (+3079 additions, -5 deletions)

View changed files

➕ .gitignore (+2 -0)
➕ CNAME (+1 -0)
➕ Gemfile (+41 -0)
➕ Gemfile.lock (+161 -0)
➕ Procfile (+1 -0)
📝 README.md (+36 -5)
➕ Rakefile (+5 -0)
➕ _config.yml (+30 -0)
➕ _config_local.yml (+2 -0)
➕ _layouts/default.html (+48 -0)
➕ _site/CNAME (+1 -0)
➕ _site/README.md (+28 -0)
➕ _site/css/blueprint/ie.css (+35 -0)
➕ _site/css/blueprint/print.css (+29 -0)
➕ _site/css/blueprint/screen.css (+257 -0)
➕ _site/css/lang/ar.css (+30 -0)
➕ _site/css/lang/zh-CN.css (+3 -0)
➕ _site/css/lang/zh-TW.css (+3 -0)
➕ _site/css/main.css (+95 -0)
➕ _site/css/screen.css (+60 -0)

...and 30 more files

📄 Description

Using semver.org as a jumping off point, @jameswomack and I sat down this weekend and took a stab at some of the initial content for conventionalcommits.org (which I've bought the domain name for).

Here's what I think the next steps are:

  • the specification is rough (I wanted something as simple as possible, but that the existing angular convention would fit within) I would love help with fleshing things out (and opinions on the general direction) Folks should provide feedback about content in ./index.md.
  • I've bought conventionalcommits.org, but need to put up a redirector with TLS for it ... Does anyone have an opinion about the easiest/cheapest (ideally free_ist_) way to terminate SSL for a GitHub page? -- this is made somewhat more complicated by the fact that I'm not using the conventional-changelog.github.io URL I believe (I think some sites like CloudFlare assume you are using this canonical address).
  • Once we have an initial spec up that we're happy with, I was planning on updating standard-version's documentation to reference this spec in its documentation (@evocateur perhaps we could also update the docs for the --conventional-commits flag we added to lerna?, and @jameswomack perhaps you could update unleash's docs?).
  • Do we want to use something other than Jekyll? @JaKXz want to take a stab at doing something in React with the same feature set (the ability to translate to multiple languages, support multiple spec versions mainly, linkable section headings).

I'm excited about this spec! I think we're putting a flag in the ground for the community, and regardless of the release management tool people use, this will help encourage more standardization between projects.

Look forward to feedback, CC: @JaKXz, @evocateur, @Tapppi, @stevemao, @jameswomack, @boennemann, @ajoslin.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/conventional-commits/conventionalcommits.org/pull/2 **Author:** [@bcoe](https://github.com/bcoe) **Created:** 4/3/2017 **Status:** ✅ Merged **Merged:** 4/8/2017 **Merged by:** [@bcoe](https://github.com/bcoe) **Base:** `master` ← **Head:** `conventional-commits-spec` --- ### 📝 Commits (10+) - [`ba53297`](https://github.com/conventional-commits/conventionalcommits.org/commit/ba532977726fbf30cd15adebe3216e59ac51d5a2) feat: use semver.org as a basis for conventionalcommits.org - [`af3cfd3`](https://github.com/conventional-commits/conventionalcommits.org/commit/af3cfd37b3cc80d3ad33864d92dba6dc8596bf9a) chore: fix typo unlease -> unleash - [`8402359`](https://github.com/conventional-commits/conventionalcommits.org/commit/8402359ae9ced578214cdeba3904a21da36909c0) docs: add clarifications to FAQ (#6) - [`1535443`](https://github.com/conventional-commits/conventionalcommits.org/commit/15354437eb99ed7e36c080a0c549cf7001734191) chore: switch to using Jekyll plugins directly, rather than using github-pages (#7) - [`69e0477`](https://github.com/conventional-commits/conventionalcommits.org/commit/69e04772a16c60c7ec370312069bcd2e2785c5d0) chore: another pass of edits - [`3566644`](https://github.com/conventional-commits/conventionalcommits.org/commit/3566644de1eb1bcc838f6138f2f8466b0a15cea7) chore: a couple more edits based on @stevemao's feedback - [`8281112`](https://github.com/conventional-commits/conventionalcommits.org/commit/8281112a14b0343dde3121ffa2803914697bb3ec) docs: captitalize semver appropriately - [`5dd9294`](https://github.com/conventional-commits/conventionalcommits.org/commit/5dd929402023610a78e03771b8925e028763a0f5) docs: fix typo - [`877d8ec`](https://github.com/conventional-commits/conventionalcommits.org/commit/877d8ecb867c7db765aa67cbc300fd153fc7bafe) docs: reason's 5 and 6 were pretty close, I think we can drop one - [`0d9c350`](https://github.com/conventional-commits/conventionalcommits.org/commit/0d9c35009cf83f8c7a9759cb5cc64365ebcf02a5) docs: rephrase one of the FAQ questions a bit ### 📊 Changes **50 files changed** (+3079 additions, -5 deletions) <details> <summary>View changed files</summary> ➕ `.gitignore` (+2 -0) ➕ `CNAME` (+1 -0) ➕ `Gemfile` (+41 -0) ➕ `Gemfile.lock` (+161 -0) ➕ `Procfile` (+1 -0) 📝 `README.md` (+36 -5) ➕ `Rakefile` (+5 -0) ➕ `_config.yml` (+30 -0) ➕ `_config_local.yml` (+2 -0) ➕ `_layouts/default.html` (+48 -0) ➕ `_site/CNAME` (+1 -0) ➕ `_site/README.md` (+28 -0) ➕ `_site/css/blueprint/ie.css` (+35 -0) ➕ `_site/css/blueprint/print.css` (+29 -0) ➕ `_site/css/blueprint/screen.css` (+257 -0) ➕ `_site/css/lang/ar.css` (+30 -0) ➕ `_site/css/lang/zh-CN.css` (+3 -0) ➕ `_site/css/lang/zh-TW.css` (+3 -0) ➕ `_site/css/main.css` (+95 -0) ➕ `_site/css/screen.css` (+60 -0) _...and 30 more files_ </details> ### 📄 Description Using semver.org as a jumping off point, @jameswomack and I sat down this weekend and took a stab at some of the initial content for conventionalcommits.org (which I've bought the domain name for). Here's what I think the next steps are: - [x] the specification is rough (I wanted something as simple as possible, but that the existing angular convention would fit within) I would love help with fleshing things out (and opinions on the general direction) Folks should provide feedback about content in `./index.md`. - [x] I've bought conventionalcommits.org, but need to put up a redirector with TLS for it ... Does anyone have an opinion about the easiest/cheapest (ideally free_ist_) way to terminate SSL for a GitHub page? -- this is made somewhat more complicated by the fact that I'm not using the `conventional-changelog.github.io` URL I believe (I think some sites like CloudFlare assume you are using this canonical address). - [ ] Once we have an initial spec up that we're happy with, I was planning on updating standard-version's documentation to reference this spec in its documentation (@evocateur perhaps we could also update the docs for the `--conventional-commits` flag we added to lerna?, and @jameswomack perhaps you could update unleash's docs?). - [ ] Do we want to use something other than Jekyll? @JaKXz want to take a stab at doing something in React with the same feature set (the ability to translate to multiple languages, support multiple spec versions mainly, linkable section headings). I'm excited about this spec! I think we're putting a flag in the ground for the community, and regardless of the release management tool people use, this will help encourage more standardization between projects. Look forward to feedback, CC: @JaKXz, @evocateur, @Tapppi, @stevemao, @jameswomack, @boennemann, @ajoslin. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-02-17 11:55:22 -06:00
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 pull-request
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#237
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?