The incident management steps I have in mind when being on-call and getting an alert are:
- Verify the issue
- Triage
- Communicate and scalate if needed
- Mitigate
last-dev
/ create_pr.sh
Last active
July 5, 2025 05:41
— forked from slavingia/create_pr.sh
Create a (draft) pull request using GitHub CLI
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
| #!/bin/bash | |
| # Create a (draft) pull request using GitHub CLI. | |
| # It assigns the PR to the current user, fills in the title from the first commit, | |
| # and uses the PR template file for the description. | |
| #################### PR Template: | |
| # **What** | |
| # | |
| # - [ ] Atomic change #1 |
last-dev
/ Troubleshooting.md
Created
October 19, 2024 17:44
— forked from fduran/Troubleshooting.md
last-dev
/ better-git-branch.sh
Created
February 12, 2024 07:41
— forked from schacon/better-git-branch.sh
Better Git Branch output
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
| #!/bin/bash | |
| # Colors | |
| RED='\033[0;31m' | |
| GREEN='\033[0;32m' | |
| NO_COLOR='\033[0m' | |
| BLUE='\033[0;34m' | |
| YELLOW='\033[0;33m' | |
| NO_COLOR='\033[0m' |