-
Notifications
You must be signed in to change notification settings - Fork 7.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix CHANGELOG link for #426 to point to correct PR #590
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hiya, thanks for this change, could you also update the changelog with todays date, this PR and a bit of wording? Thank you |
OK! |
davidkharbin
added a commit
to davidkharbin/Adv360-Pro-ZMK
that referenced
this pull request
Jan 10, 2025
Fix CHANGELOG link for KinesisCorporation#426 to point to correct PR (KinesisCorporation#590)
davidkharbin
added a commit
to davidkharbin/Adv360-Pro-ZMK
that referenced
this pull request
Jan 10, 2025
Fix CHANGELOG link for KinesisCorporation#426 to point to correct PR (KinesisCorporation#590)
wayneeseguin
added a commit
to wayneeseguin/Adv360-Pro-ZMK
that referenced
this pull request
Jan 15, 2025
Fix CHANGELOG link for KinesisCorporation#426 to point to correct PR (KinesisCorporation#590)
wrightgardner
pushed a commit
to wrightgardner/Adv360-Pro-ZMK
that referenced
this pull request
Jan 20, 2025
…inesisCorporation#590) * point CHANGELOG entry for KinesisCorporation#426 at correct PR * Update changelog for changelog change
Jesperoka
added a commit
to Jesperoka/Adv360-Pro-ZMK
that referenced
this pull request
Jan 21, 2025
Fix CHANGELOG link for KinesisCorporation#426 to point to correct PR (KinesisCorporation#590)
gurupanguji
added a commit
to gurupanguji/Adv360-Pro-ZMK
that referenced
this pull request
Jan 24, 2025
Fix CHANGELOG link for KinesisCorporation#426 to point to correct PR (KinesisCorporation#590)
gurupanguji
added a commit
to gurupanguji/Adv360-Pro-ZMK
that referenced
this pull request
Jan 24, 2025
cpfair
pushed a commit
to cpfair/Adv360-Pro-ZMK
that referenced
this pull request
Jan 27, 2025
…inesisCorporation#590) * point CHANGELOG entry for KinesisCorporation#426 at correct PR * Update changelog for changelog change
maxclax
added a commit
to maxclax/Adv360-Pro-ZMK
that referenced
this pull request
Jan 28, 2025
Fix CHANGELOG link for KinesisCorporation#426 to point to correct PR (KinesisCorporation#590)
markohara
pushed a commit
to markohara/Adv360-Pro-ZMK
that referenced
this pull request
Feb 2, 2025
…inesisCorporation#590) * point CHANGELOG entry for KinesisCorporation#426 at correct PR * Update changelog for changelog change
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Advantage 360 Pro PR template
What's changed:
The CHANGELOG.md entry for #426 is updated, it was incorrectly pointing to an unrelated PR #424 that was closed and not merged.
Why has this change been implemented:
I noticed after clicking the link in the changelog that it took me to an unrelated keymap update PR.
What (if any) actions must a user take after this change:
None