heygrady Github contribution chart
heygrady Github Stats
heygrady Most Used Languages

Activity

22 Sep 2022

Heygrady

chore: remove src from inputs in turbo.json

Pushed On 22 Sep 2022 at 07:46:11

Heygrady

chore: upgrade dependencies

Pushed On 22 Sep 2022 at 07:01:19

Heygrady

Version Packages

Pushed On 03 Sep 2022 at 08:29:13
Pull Request

Heygrady

Version Packages

Created On 03 Sep 2022 at 08:29:13

Heygrady

fix(blog-app): tweak hero image

Pushed On 03 Sep 2022 at 08:27:38

Heygrady

chore: add changeset

Pushed On 03 Sep 2022 at 08:27:38

Heygrady

Version Packages

Pushed On 03 Sep 2022 at 07:34:12
Pull Request

Heygrady

Version Packages

Created On 03 Sep 2022 at 07:34:11

Heygrady

chore: configure yarn for all tasks

Pushed On 03 Sep 2022 at 07:31:44

Heygrady

fix(blog-app): add regustry config

Pushed On 03 Sep 2022 at 07:31:44

Heygrady

chore: add changeset

Pushed On 03 Sep 2022 at 07:31:44

Heygrady

chore: add registry config back to release setp

Pushed On 03 Sep 2022 at 07:25:37

Heygrady

Version Packages

Pushed On 03 Sep 2022 at 07:20:10
Pull Request

Heygrady

Version Packages

Created On 03 Sep 2022 at 07:20:10

Heygrady

chore: update firebase config

Pushed On 03 Sep 2022 at 07:18:14

Heygrady

chore: remove trailing slash from .npmrc

Pushed On 03 Sep 2022 at 07:18:14

Heygrady

chore: tweak publish settings

Pushed On 03 Sep 2022 at 07:18:14

Heygrady

chore: add changeset

Pushed On 03 Sep 2022 at 07:18:14

Heygrady

Version Packages

Pushed On 03 Sep 2022 at 07:08:17
Pull Request

Heygrady

Version Packages

Created On 03 Sep 2022 at 07:08:16

Heygrady

feat(create-post): rename package, command module format

Pushed On 03 Sep 2022 at 07:05:59

Heygrady

chore: properly configure yarn in Github actions

Pushed On 03 Sep 2022 at 07:05:59

Heygrady

chore: upgrade packages

Pushed On 03 Sep 2022 at 07:05:59

Heygrady

fix(blog-app): force trailing slash on links

Pushed On 03 Sep 2022 at 07:05:59

Heygrady

fix(blog-app): properly configure yarn in github actions

Pushed On 03 Sep 2022 at 07:05:59

Heygrady

chore(blog-app): rename blog folder to blog-app

Pushed On 03 Sep 2022 at 07:05:59

Heygrady

chore: update yarn.lock

Pushed On 03 Sep 2022 at 07:05:59

Heygrady

chore: add changeset

Pushed On 03 Sep 2022 at 07:05:59

Heygrady

fix: typo

Pushed On 03 Sep 2022 at 02:45:33

Heygrady

chore: fix typo

Pushed On 03 Sep 2022 at 02:45:33

Heygrady

Version Packages

Pushed On 03 Sep 2022 at 01:54:32
Pull Request

Heygrady

Version Packages

Created On 03 Sep 2022 at 01:54:30

Heygrady

fix(blog-app): add google analytics

Pushed On 03 Sep 2022 at 01:52:41

Heygrady

chore: add changeset

Pushed On 03 Sep 2022 at 01:52:41

Heygrady

Version Packages

Pushed On 03 Sep 2022 at 01:45:21
Pull Request

Heygrady

Version Packages

Created On 03 Sep 2022 at 01:45:16

Heygrady

feat(blog-app): init firebase app

Pushed On 03 Sep 2022 at 01:43:40

Heygrady

chore: update yarn.lock

Pushed On 03 Sep 2022 at 01:43:40

Heygrady

chore: add changeset

Pushed On 03 Sep 2022 at 01:43:40

Heygrady

Add support for conventional-recommended-bump

Add conventional recommended bump

Picking versions manually is boring when you're already using conventional commits in your repository.

This PR adds some flags to enable using conventional-recommended-bump.

The purpose is to cover the use-case outlined in https://github.com/changesets/changesets/issues/862 (but in a way that matches how Changesets currently works).

This feature was heavily inspired by @lerna/conventional-commits. People asking for this feature have already adopted conventional commits in their workflows.

Goals:

  1. Enable conventional commits for version bumps
  2. Enable creation of changesets without user interaction
  3. Don't break the existing workflow
# Create a changeset without answering any questions
yarn changeset add --all-changed --recommend --message "Amazing!" --yes 

New flags:

  • --all -- selects all changed and unchanged packages
  • --all-changed -- selects only changed packages
  • --all-unchanged -- selects only the unchanged packages
  • --message -- used for the summary of the changeset
  • --recommend -- automatically recommends the version bump using conventional commits
  • --yes -- skips all confirmations to enable adding a changeset with zero interactions

New Config

Users will need to opt-in to using conventional commits by adding a preset to the .changesets/config.json. This preset is only used for recommending version bumps and will not otherwise affect the changelog that gets generated.

Example: Default preset

This example shows the .changeset/config.json from the changesets repo with conventional commits enabled.

{
  "changelog": [
    "@changesets/changelog-github",
    { "repo": "changesets/changesets" }
  ],
  "conventionalCommits": true,
  "baseBranch": "main",
  "commit": false,
  "access": "public",
  "___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {
    "updateInternalDependents": "always"
  }
} 

Forked On 02 Sep 2022 at 11:29:18

Heygrady

I'm going to be rethinking my approach here. I've been playing more with changesets on a personal project and I can see some issues. You make an excellent point about the difficulty of testing conventional commits behavior. It may be considered out of scope to do full integration testing of conventional commits as it can be presumed that conventional commits is testing itself. For clarity... "would meet the user's expectations" was referring to the exact rig you are recommending. Most competing release management tools that support conventional commits also support named presets. I'm simply not aware of any competing standards that would warrant making the version bump interface within changesets wholly generic. People are either using conventional commits or they aren't. I did fine one case where [release-please](https://github.com/googleapis/release-please) supports conventional commits but does not support changing the preset. However, they _are_ using a conventional-changelog preset under the hood. There are lots of examples of tools similar to changesets that support conventional-changelog presets. For example, semantic release allows you to provide a `preset` key [like this](https://github.com/semantic-release/commit-analyzer#usage): ```json { "plugins": [ ["@semantic-release/commit-analyzer", { "preset": "angular", }] ] } ``` Other tools, like commitlint ([see here](https://commitlint.js.org/#/reference-configuration?id=javascript)) offer similar settings. ```js module.exports = { parserPreset: 'conventional-changelog-atom', } ``` Similarly, Lerna ([see here](https://github.com/lerna/lerna/blob/6cb8ab2d4af7ce25c812e8fb05cd04650105705f/commands/version/README.md#--changelog-preset)) supports a `changelogPreset` like this: ```json { "changelogPreset": "angular" } ``` Usually tools default to using the angular preset as the Angular community originally popularized the modern notion of conventional commits.
On 02 Sep 2022 at 11:29:18

Heygrady

Add support for conventional-recommended-bump

Add conventional recommended bump

Picking versions manually is boring when you're already using conventional commits in your repository.

This PR adds some flags to enable using conventional-recommended-bump.

The purpose is to cover the use-case outlined in https://github.com/changesets/changesets/issues/862 (but in a way that matches how Changesets currently works).

This feature was heavily inspired by @lerna/conventional-commits. People asking for this feature have already adopted conventional commits in their workflows.

Goals:

  1. Enable conventional commits for version bumps
  2. Enable creation of changesets without user interaction
  3. Don't break the existing workflow
# Create a changeset without answering any questions
yarn changeset add --all-changed --recommend --message "Amazing!" --yes 

New flags:

  • --all -- selects all changed and unchanged packages
  • --all-changed -- selects only changed packages
  • --all-unchanged -- selects only the unchanged packages
  • --message -- used for the summary of the changeset
  • --recommend -- automatically recommends the version bump using conventional commits
  • --yes -- skips all confirmations to enable adding a changeset with zero interactions

New Config

Users will need to opt-in to using conventional commits by adding a preset to the .changesets/config.json. This preset is only used for recommending version bumps and will not otherwise affect the changelog that gets generated.

Example: Default preset

This example shows the .changeset/config.json from the changesets repo with conventional commits enabled.

{
  "changelog": [
    "@changesets/changelog-github",
    { "repo": "changesets/changesets" }
  ],
  "conventionalCommits": true,
  "baseBranch": "main",
  "commit": false,
  "access": "public",
  "___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {
    "updateInternalDependents": "always"
  }
} 

Merged On 02 Sep 2022 at 11:29:19

Heygrady

Commented On 02 Sep 2022 at 11:29:19

Heygrady

chore: rename default branch to main

Pushed On 02 Sep 2022 at 10:47:33
Create Branch
Heygrady In heygrady/blog Create Branchmain

Heygrady

Description not entered by the user.

On 02 Sep 2022 at 10:43:42

Heygrady

Version Packages

Pushed On 02 Sep 2022 at 10:41:43
Pull Request

Heygrady

Version Packages

Created On 02 Sep 2022 at 10:41:42