Skip to content

feat: implement /assign GitHub Action#75

Open
shashank2k5 wants to merge 1 commit into
Dev-Card:mainfrom
shashank2k5:main
Open

feat: implement /assign GitHub Action#75
shashank2k5 wants to merge 1 commit into
Dev-Card:mainfrom
shashank2k5:main

Conversation

@shashank2k5
Copy link
Copy Markdown

Summary

This PR implements a GitHub Action that allows contributors to self-assign issues and pull requests using the /assign command. This automation reduces maintainer workload by enabling instant task ownership directly from the comment section.

Closes #


Type of Change

  • New feature
  • Documentation
  • Infrastructure / DevOps

What Changed

  • .github/workflows/assign.yml: Created a new workflow that parses /assign commands using actions/github-script. It handles self-assignment, mention-based assignment (/assign @user), duplicate prevention, and validation of GitHub usernames.
  • CONTRIBUTING.md: Added a new "Self-Assigning Issues & PRs" section to guide new contributors on how to use the command and updated the PR process workflow.

How to Test

  1. Push this branch to your GitHub repository.
  2. Navigate to an open Issue or PR on GitHub.
  3. Post a comment with the text /assign.
  4. Verify that the GitHub Actions bot assigns you to the item and replies with a confirmation message.
  5. Try edge cases: Test /assign @username for another user or /assign on an item you are already assigned to.

Checklist

  • My code follows the project's coding style.
  • I have updated documentation where necessary.
  • No new console.log or debug statements left in the code.
  • Breaking changes are documented in this PR description.

Additional Context

The workflow uses github-token: ${{ secrets.GITHUB_TOKEN }} which has the necessary permissions defined in the YAML file (issues: write, pull-requests: write). It is designed to ignore bot comments to prevent infinite loops.

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