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.

Sign up for GitHub

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

Jump to bottom

extend documentation in regards to the auto-extend-activation-time label #972

Merged
merged 1 commit into from
Sep 18, 2024
Merged

extend documentation in regards to the auto-extend-activation-time label #972

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,8 @@ namespace _lifecycle_:
- you may also get more than 2 days, but don't make that your default action, think about the trees 🌳

### extend activation time by adding a label to your pr:
⚠️ **Important: The auto-extend-activation-time label should only be used when absolutely necessary, such as when you need to activate the namespace for e2e tests.** Avoid using it as a precautionary measure to prevent unnecessary rollouts and resource consumption.

This method is effective for each unique PR. If you have multiple PRs from the same branch across various repositories, you only need to apply this setting once.
1. Navigate to the PR you wish to automatically extend its namespace's activation time.
2. Apply the `auto-extend-activation-time` label to the PR. This action will also initiate a new rollout.
Expand Down
Loading