- Simplified workflow by removing redundant steps and streamlining the process.
- Enhanced output by adding a commit message step to provide better context for future reference.
- Improved code readability and maintainability by removing unnecessary steps and focusing on essential actions.
- Added a new step to the release workflow that sets a commit message variable.
- This step ensures that the commit message is captured and stored for future reference.
- The commit message is retrieved using the `steps.commit-message.outputs.COMMIT_MESSAGE` variable.
Update release workflow to use commit message variable
- Updated the release workflow to use the commit message variable.
- This change ensures that the commit message is used when creating a release.
- The commit message is now stored in the `$GITHUB_OUTPUT` file and can be accessed by other steps in the workflow.
- Replace newline characters with line breaks in commit message body.
- Enhance readability by using a single line break between each line of the commit message.
- The workflow has been updated to use environment variables instead of hardcoded values.
- This change improves the flexibility and maintainability of the workflow.
- The changes include using `$GITHUB_OUTPUT` to store the commit message and `$COMMIT_MESSAGE` to retrieve it.
- Updated the release workflow to use a more efficient method for setting the commit message.
- Added a new task to the VSCode tasks.json file to create a new release with a dynamic tag based on the current date and
time.
These changes improve the efficiency and automation of the release process, ensuring that releases are created with accurate
and up-to-date information.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.