Skip to content

Instantly share code, notes, and snippets.

View mrclrchtr's full-sized avatar
:octocat:
Discovering new things!

Marcel Richter mrclrchtr

:octocat:
Discovering new things!
View GitHub Profile
@mrclrchtr
mrclrchtr / delete_crds.sh
Last active March 20, 2024 02:11
Remove finalizers and delete CRDs
kubectl get crd | \
grep longhorn | \
perl -anle 'print $F[0]' | \
while read -r crd ;
do
kubectl patch crd "$crd" -p '{"metadata":{"finalizers":null}}';
kubectl delete crd "$crd";
done
@mrclrchtr
mrclrchtr / commit-prompt.md
Last active March 21, 2024 19:43
ChatGPT - Create Conventional Commit Message - ai-commits-intellij-plugin

Create a commit message based on the Conventional Commit Convention using the provided 'git diff --staged' output. The message should succinctly summarize the changes and their impact, following these guidelines:

  • Title: Start with a commit type (e.g., fix, feat, refactor), include an optional scope in parentheses, and add a concise description within 74 characters, not ending with a period.
  • Body: Provide more context or rationale behind the changes with detailed descriptions or bullet points.
  • Footer: Add metadata like BREAKING CHANGE, Closes #<issue_id>, etc., if appropriate.
  • Issue ID: If and only if available, include the issue ID from '{branch}' in the Closes #<issue_id>, else don't!
  • Language: Write the commit message in '{locale}'.
  • Emojis: Incorporate relevant emojis to enhance the message, if appropriate.
  • Line Breaks: Insert line breaks thoughtfully, mainly after periods.
  • Semantic Release: Ensure the message aligns with semantic release guidelines for class