Skip to content

Conversation

@lwjohnst86
Copy link
Member

Description

Just a bit more detail about how the releases work.

Closes #106

Needs a quick review.

Checklist

  • Formatted Markdown
  • Ran just run-all

@lwjohnst86 lwjohnst86 requested a review from a team as a code owner November 7, 2025 11:28
@lwjohnst86 lwjohnst86 moved this from Todo to In Review in Iteration planning Nov 7, 2025
Copy link

@joelostblom joelostblom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two minor typos, otherwise looks good!

will not have many changes within it. Below is a list of releases along
with what was changed within it.
to be able to automatically create these releases, which uses
[SemVar](https://semverdoc.org) as the version numbering scheme.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
[SemVar](https://semverdoc.org) as the version numbering scheme.
[SemVer](https://semverdoc.org) as the version numbering scheme.

will not have many changes within it. Below is a list of releases along
with what was changed within it.
to be able to automatically create these releases, which uses
[SemVar](https://semverdoc.org) as the version numbering scheme.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
[SemVar](https://semverdoc.org) as the version numbering scheme.
[SemVer](https://semverdoc.org) as the version numbering scheme.

Copy link
Member

@signekb signekb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice with some elaboration. I've added a couple of suggestions below:

Comment on lines +4 to +6
Commits](https://decisions.seedcase-project.org/why-conventional-commits)
when writing commit messages, we're able to automatically create formal
"releases" of the website based on the commit messages. Releases in the
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Commits](https://decisions.seedcase-project.org/why-conventional-commits)
when writing commit messages, we're able to automatically create formal
"releases" of the website based on the commit messages. Releases in the
Commits](https://decisions.seedcase-project.org/why-conventional-commits),
we're able to automatically create formal
"releases" of the website based on our commit messages. Releases in the

often, sometimes several in a day. It also means any individual release
will not have many changes within it. Below is a list of releases along
with what was changed within it.
to be able to automatically create these releases, which uses
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
to be able to automatically create these releases, which uses
to automatically create these releases using

Comment on lines +13 to +14
Because releases are created based on commit messages, we release quite
often, sometimes several times in a day. This also means that any
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Because releases are created based on commit messages, we release quite
often, sometimes several times in a day. This also means that any
Because releases are created based on commit messages, a new release is created quite
often---sometimes several times in a day. This also means that any

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comments as above ⏫

@github-project-automation github-project-automation bot moved this from In Review to In Progress in Iteration planning Nov 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

Add more explanation about release process in template's CHANGELOG

4 participants