Skip to content

chore: Allow "Impacts: none"#843

Merged
kkowalski-reef merged 1 commit intomasterfrom
mateusz/explicit-impacts-none
Feb 17, 2026
Merged

chore: Allow "Impacts: none"#843
kkowalski-reef merged 1 commit intomasterfrom
mateusz/explicit-impacts-none

Conversation

@mateuszsrebrny-reef
Copy link
Contributor

In this PR:

  • git commit linter gets to accept "Impacts: none"
  • it doesn't accept mixing none with real projects

@mateuszsrebrny-reef mateuszsrebrny-reef force-pushed the mateusz/explicit-impacts-none branch from f69d057 to 6e741ba Compare February 17, 2026 08:55
@github-actions
Copy link

Commit message lint report

gitlint --commits cbab476f0c77c200fff78a82c8af22f4f1c7d843..6e741ba0bb34b2ae2f83084a7f7a012043dcab27

Status: ✅ No issues found.

@kkowalski-reef kkowalski-reef merged commit 5f32f9c into master Feb 17, 2026
32 of 34 checks passed
@kkowalski-reef kkowalski-reef deleted the mateusz/explicit-impacts-none branch February 17, 2026 09:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments