Feat no slashes in branches #23
Merged
Conversation
This file contains hidden or 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
# [1.3.0-feat-no-slashes-in-branches.1](v1.2.41...v1.3.0-feat-no-slashes-in-branches.1) (2025-04-04) ### Bug Fixes * **centalising yaml:** yaml ([8334d02](8334d02)) * **commit history git ui commits break semver:** fix semver ([a6ef9e3](a6ef9e3)) * **dddd:** gggg ([9295645](9295645)) * **eurggh:** ee ([5c7212d](5c7212d)) * **go:** go ([1a3faf0](1a3faf0)) * **more debugging:** jhfhf ([9d934f9](9d934f9)) * **post version reset does it work:** sdh ([08a55c1](08a55c1)) * **spacing:** ffhf ([67bbd20](67bbd20)) * **yml:** still trying to fix ([0f7ad99](0f7ad99)) ### Features * **123:** feat ([c525139](c525139)) * **dev:** dev ([17468c7](17468c7)) * **just try:** sdf ([04cd1c8](04cd1c8)) * **sd:** ff is release intearing ([85d1d71](85d1d71)) * **semver still:** lets go ([f2f87cd](f2f87cd)) * **seperate yml pr release dev:** gogogo ([6b7d1cb](6b7d1cb)) * **slashless:** googog ([11a8e5b](11a8e5b)) * **tags been set elsewhere may fix itself:** dsfjb ([1411625](1411625))
…nologyEnhancedLearning/GitPageBlazorWASM into feat-no-slashes-in-branches
# [1.3.0-feat-no-slashes-in-branches.2](v1.3.0-feat-no-slashes-in-branches.1...v1.3.0-feat-no-slashes-in-branches.2) (2025-04-04) ### Features * **plz:** plz ([4420cae](4420cae))
…nologyEnhancedLearning/GitPageBlazorWASM into feat-no-slashes-in-branches
# [1.3.0-feat-no-slashes-in-branches.3](v1.3.0-feat-no-slashes-in-branches.2...v1.3.0-feat-no-slashes-in-branches.3) (2025-04-04) ### Features * **ddd:** ddd ([d6331f1](d6331f1))
# [1.3.0-feat-no-slashes-in-branches.4](v1.3.0-feat-no-slashes-in-branches.3...v1.3.0-feat-no-slashes-in-branches.4) (2025-04-04) ### Bug Fixes * **token:** unlikely ([182cd83](182cd83))
# [1.3.0-feat-no-slashes-in-branches.5](v1.3.0-feat-no-slashes-in-branches.4...v1.3.0-feat-no-slashes-in-branches.5) (2025-04-04) ### Bug Fixes * **goes:** nothing ([4a02265](4a02265))
…nologyEnhancedLearning/GitPageBlazorWASM into feat-no-slashes-in-branches
# [1.3.0-feat-no-slashes-in-branches.6](v1.3.0-feat-no-slashes-in-branches.5...v1.3.0-feat-no-slashes-in-branches.6) (2025-04-04) ### Features * **desperate:** without debug as new weird error ([b653585](b653585))
…nologyEnhancedLearning/GitPageBlazorWASM into feat-no-slashes-in-branches
# [1.3.0-feat-no-slashes-in-branches.7](v1.3.0-feat-no-slashes-in-branches.6...v1.3.0-feat-no-slashes-in-branches.7) (2025-04-04) ### Bug Fixes * **where really is the error:** error ([65971d8](65971d8))
# [1.3.0-feat-no-slashes-in-branches.9](v1.3.0-feat-no-slashes-in-branches.8...v1.3.0-feat-no-slashes-in-branches.9) (2025-04-04) ### Features * **gogog:** gogog ([7b6f5f9](7b6f5f9))
…nologyEnhancedLearning/GitPageBlazorWASM into feat-no-slashes-in-branches
# [1.3.0-feat-no-slashes-in-branches.10](v1.3.0-feat-no-slashes-in-branches.9...v1.3.0-feat-no-slashes-in-branches.10) (2025-04-04) ### Bug Fixes * **ttt:** fgh ([41229ff](41229ff))
…nologyEnhancedLearning/GitPageBlazorWASM into feat-no-slashes-in-branches
…nologyEnhancedLearning/GitPageBlazorWASM into feat-no-slashes-in-branches
# [1.3.0-feat-no-slashes-in-branches.13](v1.3.0-feat-no-slashes-in-branches.12...v1.3.0-feat-no-slashes-in-branches.13) (2025-04-04) ### Features * **dfsd:** looop ([320ea67](320ea67)) * **dggg:** gggg ([101fea4](101fea4))
…nologyEnhancedLearning/GitPageBlazorWASM into feat-no-slashes-in-branches
# [1.3.0-feat-no-slashes-in-branches.14](v1.3.0-feat-no-slashes-in-branches.13...v1.3.0-feat-no-slashes-in-branches.14) (2025-04-04) ### Features * **should work:** please ([bfb52e1](bfb52e1))
# [1.3.0-feat-no-slashes-in-branches.15](v1.3.0-feat-no-slashes-in-branches.14...v1.3.0-feat-no-slashes-in-branches.15) (2025-04-07) ### Features * **branch regulation:** ci really ([2e9d50a](2e9d50a)) * **hmm:** ok meb ([099cf76](099cf76))
There was a problem hiding this comment.
Copilot reviewed 4 out of 6 changed files in this pull request and generated 2 comments.
Files not reviewed (2)
- .del-releaserc.txt: Language not supported
- .releaserc.json: Language not supported
Comments suppressed due to low confidence (2)
.github/workflows/pull_request.yml:28
- Changing commitlint to 'continue-on-error: true' might allow commit lint errors to pass silently. Revert to 'false' if strict commit validation is required.
continue-on-error: true
.github/workflows/dev.yml:57
- The branch-name-check step uses 'continue-on-error: false' in the dev workflow, which is inconsistent with the pull_request workflow's setting of true. Please verify that this difference is intentional.
continue-on-error: false
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
testing pull request erules