Rulepython

Git Workflow Rule

This repository has branch protection enabled on `main`. Direct pushes are blocked.

View Source

Git Workflow

This repository has branch protection enabled on main. Direct pushes are blocked.

Making Changes

  1. Create a feature branch from the current commit:

    git checkout -b <branch-name>
    
  2. Push the branch to origin:

    git push -u origin <branch-name>
    
  3. Create a pull request:

    gh pr create --title "<type>(<scope>): <description>" --body "Description here"
    
  4. Wait for status checks (MegaLinter must pass)

  5. Merge after approval (or user self-approves if they have permission)

Branch Naming

Use <type>/<description> format matching conventional commit types:

  • feat/<feature-name> - New features
  • fix/<issue> - Bug fixes
  • docs/<topic> - Documentation changes
  • ci/<change> - CI/CD changes
  • refactor/<change> - Code restructuring
  • test/<change> - Test updates
  • chore/<task> - Maintenance tasks
  • build/<change> - Build system changes

Important

  • Never attempt git push directly to main
  • Always go through the PR workflow
  • MegaLinter status check is required before merge