Skip to content
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

chore: temporarily disable release-please #1074

Merged
merged 1 commit into from
Mar 4, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions .github/workflows/management-changelog.yml
Original file line number Diff line number Diff line change
@@ -1,10 +1,11 @@
on:
push:
branches:
- main # Your main branch
- dev # Your development branch
- release/* # Your releases branch
- v2 # Temp V2 integration branch
branches: []
# branches:
# - main # Your main branch
# - dev # Your development branch
# - release/* # Your releases branch
# - v2 # Temp V2 integration branch
Comment on lines +3 to +8
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The branch-specific triggers for the workflow have been commented out, effectively disabling the automated process for generating changelogs and managing releases. While this achieves the objective of temporarily halting these processes, consider the following points for future reference:

  • Documentation: It's important to document the reason for such changes within the workflow file or in a linked issue for clarity and future reference. This helps in understanding the context and rationale behind temporary changes.
  • Alternative Approaches: If the disablement is intended to be temporary, consider using conditional checks within the workflow to enable or disable certain steps based on environment variables or repository settings. This approach can offer more flexibility and control without needing to comment out code.
  • Notification: Ensure that relevant stakeholders or teams are notified about this change, especially if it impacts the release process or the generation of changelogs that they might depend on.


permissions:
contents: read
Expand Down
Loading