Skip to content

chore(ci): rename PR welcome workflow and add code of conduct - #6

Closed
Atliac wants to merge 4 commits into
mainfrom
pr-guidance
Closed

chore(ci): rename PR welcome workflow and add code of conduct#6
Atliac wants to merge 4 commits into
mainfrom
pr-guidance

Conversation

@Atliac

@Atliac Atliac commented Jun 21, 2026

Copy link
Copy Markdown
Owner
  • Rename .github/workflows/pr-welcome.yml to pr-guidance.yml
  • Add standard CODE_OF_CONDUCT.md to the repository

- Rename `.github/workflows/pr-welcome.yml` to `pr-guidance.yml`
- Add standard `CODE_OF_CONDUCT.md` to the repository
@coderabbitai

coderabbitai Bot commented Jun 21, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 92405933-2bda-445a-946f-86ee36f1a671

📥 Commits

Reviewing files that changed from the base of the PR and between 6260367 and 03d8bc6.

📒 Files selected for processing (1)
  • .github/workflows/pr-guidance.yml

📝 Walkthrough

Summary by CodeRabbit

  • Documentation

    • Added a complete Code of Conduct (Contributor Covenant) covering community standards, reporting expectations, and enforcement approach.
  • Chores

    • Introduced a new automated pull request guidance comment that posts structured review-time instructions and only posts once per pull request.
    • Removed the older pull request welcome automation to avoid sending outdated guidance comments.

Walkthrough

Removes .github/workflows/pr-welcome.yml and replaces it with a new .github/workflows/pr-guidance.yml workflow that posts an expanded automated guidance comment on PRs. Also adds a CODE_OF_CONDUCT.md implementing the Contributor Covenant.

Changes

Repository Community Health Files

Layer / File(s) Summary
PR guidance workflow trigger and permissions
.github/workflows/pr-guidance.yml
Workflow triggers on pull_request_target for opened and ready_for_review events with contents: read and issues: write permissions.
Comment deduplication and context setup
.github/workflows/pr-guidance.yml
Job script extracts the PR number from the event payload, lists existing issue comments, detects an existing Atliac-signed automated message to prevent duplicates, and computes the documentation base URL from the PR base branch.
Guidance message construction and posting
.github/workflows/pr-guidance.yml
Builds a multi-section Markdown body with welcome header, contributor checklist, collapsible <details> blocks for contributors, community reviewers, and maintainers (including shell/CLI examples), a "Helpful Resources" section, signature footer, and posts the comment via github.rest.issues.createComment.
Code of Conduct
CODE_OF_CONDUCT.md
Adds the full Contributor Covenant Code of Conduct with pledge, standards, scope, enforcement responsibilities, enforcement guidelines, and a placeholder reporting contact method.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

  • Atliac/crate-template#5: Introduced the original pr-welcome.yml workflow using the same duplicate-detection pattern (checking for the Atliac-signed comment before posting), which this PR supersedes with pr-guidance.yml.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the two main changes: renaming the PR welcome workflow to pr-guidance and adding a code of conduct file.
Description check ✅ Passed The description directly relates to the changeset, listing the two primary changes: workflow rename and addition of CODE_OF_CONDUCT.md.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch pr-guidance

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4


ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b9797bec-8e91-49c5-bce4-bbc5542d13ab

📥 Commits

Reviewing files that changed from the base of the PR and between 6cb7d2f and 97e1d0e.

📒 Files selected for processing (3)
  • .github/workflows/pr-guidance.yml
  • .github/workflows/pr-welcome.yml
  • CODE_OF_CONDUCT.md
💤 Files with no reviewable changes (1)
  • .github/workflows/pr-welcome.yml

Comment thread .github/workflows/pr-guidance.yml
Comment thread .github/workflows/pr-guidance.yml
Comment thread .github/workflows/pr-guidance.yml
Comment thread CODE_OF_CONDUCT.md
Repository owner deleted a comment from github-actions Bot Jun 21, 2026
Repository owner deleted a comment from github-actions Bot Jun 21, 2026
Atliac added 2 commits June 21, 2026 19:17
The pull_request event runs with a restricted token that cannot create
comments on PRs from forks. Switching to pull_request_target runs the
workflow in the base repository's context with proper write permissions,
enabling the guidance comment to be posted on fork PRs.
@Atliac Atliac closed this Jun 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant