Skip to content

th30d4y/.github

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

20 Commits
 
 
 
 

Repository files navigation

.github

Organization-wide GitHub defaults and shared automation.

Organization Issue/PR Bot rollout

This repository now provides:

  • A centralized reusable workflow: .github/workflows/org-bot.yml
  • A workflow template for other repositories: .github/workflow-templates/org-bot-caller.yml

1) Configure organization secrets

In Organization Settings → Secrets and variables → Actions, create:

  • EMAIL_USER
  • EMAIL_PASS

Grant both secrets to all repositories that should use the bot.

2) Enable in each repository

In each target repository, add the caller workflow from template:

  • .github/workflows/org-bot-caller.yml

Or copy this minimum caller workflow:

name: Organization Issue/PR Bot Caller

on:
  issues:
    types: [opened]
  pull_request_target:
    types: [opened]

permissions:
  contents: read
  issues: write
  pull-requests: write

jobs:
  org-bot:
    uses: th30d4y/.github/.github/workflows/org-bot.yml@main
    with:
      event_type: ${{ github.event_name == 'issues' && 'Issue' || 'Pull Request' }}
      number: ${{ github.event.issue.number || github.event.pull_request.number }}
      title: ${{ github.event.issue.title || github.event.pull_request.title }}
      url: ${{ github.event.issue.html_url || github.event.pull_request.html_url }}
    secrets: inherit

Security note: this uses pull_request_target so the bot can post welcome comments on fork PRs. Keep this workflow free of checkout/build/test steps that execute PR branch code.

Tip: once you publish a stable tag for this workflow (for example v1), prefer @v1 instead of @main so repositories get controlled, versioned updates instead of inheriting breaking changes immediately.

3) Validate and roll out

  1. Enable on 1–2 repositories first.
  2. Open a test issue and a test PR to confirm:
    • welcome comment is posted
    • owner email is sent
  3. Roll out to remaining repositories.

4) Optional enforcement

If your GitHub plan supports required workflows/rulesets, enforce the caller workflow org-wide. Otherwise, each repository must include the caller workflow file.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors