refactor(release): refactoring release process a bit. #3
Conversation
Add issue templates Add release drafter Remove version files
Merging this branch will decrease overall coverage
Coverage by fileChanged files (no unit tests)
Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code. Changed unit test files
|
There was a problem hiding this comment.
Pull Request Overview
Refactors the release process by removing the existing version files, adding a Release Drafter workflow, and introducing GitHub issue templates.
- Remove hardcoded version constant and its test
- Add automated Release Drafter workflow and configuration
- Provide standardized feature request and bug report templates
Reviewed Changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| version_test.go | Deleted test for Version() |
| version.go | Deleted version constant and Version() function |
| .github/workflows/release-drafter.yml | New workflow file to auto-draft releases |
| .github/release-drafter.yml | Configuration for the Release Drafter action |
| .github/ISSUE_TEMPLATE/feature_request.md | New feature request issue template |
| .github/ISSUE_TEMPLATE/config.yml | Settings to disable blank issues and link docs/repo |
| .github/ISSUE_TEMPLATE/bug_report.md | New bug report issue template |
Comments suppressed due to low confidence (2)
version_test.go:1
- Removing the version test eliminates coverage for version functionality; ensure the new release process includes tests or integration checks for version resolution.
-package entraid
version.go:1
- The
Version()API and its backing constant have been removed; update any callers or provide migration guidance to prevent breaking changes.
-package entraid
| @@ -0,0 +1,26 @@ | |||
| name: Release Drafter | |||
There was a problem hiding this comment.
[nitpick] Consider adding a brief comment or linking to higher-level docs explaining how this workflow fits into the overall release and versioning process.
| @@ -0,0 +1,46 @@ | |||
| name-template: 'v$RESOLVED_VERSION' | |||
There was a problem hiding this comment.
[nitpick] Having two release-drafter configuration files in different directories may be confusing; consider consolidating them or documenting their distinct roles.
Add issue templates
Add release drafter
Remove version files