feat: add issue automation workflow and script #1367

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

roshankumar0036singh wants to merge 2 commits into Code-A2Z:main from roshankumar0036singh:feat/issue-automation

+463 −0

Contributor

roshankumar0036singh commented Jan 24, 2026

Pull Requests Review Criteria

Caution

PRs that fail to meet these review standards will be automatically flagged and may be rejected by maintainers.

Filled out this PR template properly
Did not commit directly to main
Limited commits (max 3–4 unless permitted by Admin/Mentors)
Added comments in complex parts of code

Closes:
closes #1072

Describe the add-ons or changes you've made 📃

I have implemented a comprehensive GitHub Issue Automation system to streamline contribution management.

Key Features:

Auto-Assignment: Automatically assigns issues to creators if they select "Yes" in the issue form.
/assign Command: Allows contributors to claim issues by commenting /assign.
Deadline Enforcement: A daily schedule checks assigned issues and manages timeouts based on priority:
- High: 3 days
- Medium: 6 days
- Low: 8 days
- Includes warning messages 24h before timeout.
Assignment Limits: Prevents users from hoarding more than 2 issues at a time.

Files Added:

.github/workflows/issue-automation.yml: Defines triggers (issues, comments, schedule).
.github/scripts/issue-automation.js: Contains the logic for assignment and deadline checks.

Screenshots 📷

Screenshot 2026-01-24 134942

Screenshot 2026-01-24 134953

The logic has been verified using a local test harness to mock GitHub events. The workflow requires issues: write permissions which have been added.

vercel bot commented Jan 24, 2026

@roshankumar0036singh is attempting to deploy a commit to the avdheshvarshney's projects Team on Vercel.

A member of the Team first needs to authorize it.

github-actions bot commented Jan 24, 2026

Thank you for submitting your pull request! We'll review it as soon as possible. For further communication, join our discord server https://discord.gg/tSqtvHUJzE.

Contributor Author

roshankumar0036singh commented Jan 24, 2026 •

edited

Loading

@Avdhesh-Varshney plz review it i couldnt test the functionality so just tested it locally by creating test file and mimicing the github triggers

Avdhesh-Varshney requested changes

View reviewed changes

Collaborator

Avdhesh-Varshney left a comment

Great work. Need to check whether we can process the github project using this workflow. https://github.com/orgs/Code-A2Z/projects/1

.github/scripts/issue-automation.js Outdated

+                              await assignUser(issue.number, username);
+                              await addLabels(issue.number, ['Status: Assigned']);
+                              await removeLabel(issue.number, 'up-for-grabs');

Collaborator

Avdhesh-Varshney Jan 24, 2026

Just assign to user, Don't add labels.
If possible to update the status of issue in OS - TASK TRACKER (view), try to update.

.github/scripts/issue-automation.js Outdated


		const username = issue.user.login;

		if (await checkUserAssignmentLimit(username)) {

Collaborator

Avdhesh-Varshney Jan 24, 2026

Create variable for await. It may breaks the if condition as promise is always true

.github/scripts/issue-automation.js Outdated


		const username = comment.user.login;

		if (await checkUserAssignmentLimit(username)) {

Collaborator

Avdhesh-Varshney Jan 24, 2026

same here

.github/scripts/issue-automation.js Outdated

+                              await assignUser(issue.number, username);
+                              await addLabels(issue.number, ['Status: Assigned']);
+                              await removeLabel(issue.number, 'up-for-grabs');

Collaborator

Avdhesh-Varshney Jan 24, 2026

Remove labels

.github/scripts/issue-automation.js Outdated

+                      // Handle Scheduled Deadline Checks
+                      if (context.eventName === 'schedule') {
+                          // Fetch all open issues with 'Status: Assigned'

Collaborator

Avdhesh-Varshney Jan 24, 2026

Try to fetch from OS - TASK TRACKER (view) project. Otherwise check all opened issues.

.github/scripts/issue-automation.js Outdated

+                              const warningDate = new Date(deadline);
+                              warningDate.setDate(deadline.getDate() - 1);
+                              const assignee = issue.assignees.length > 0 ? issue.assignees[0].login : null;

Collaborator

Avdhesh-Varshney Jan 24, 2026

Have you check the latest contributor is always at 0th index?
Or can we not get it from events variable? (That to be more accurate)

.github/scripts/issue-automation.js Outdated

+                              if (labels.includes('priority: high')) daysAllowed = 3;
+                              else if (labels.includes('priority: medium')) daysAllowed = 6;
+                              else if (labels.includes('priority: low')) daysAllowed = 8;

Collaborator

Avdhesh-Varshney Jan 24, 2026

Check able to check the priority from OS - TASK TRACKER (view) project?

And also check is it possible to set start date and end date of the issue, according to How much time should be allocated to this issue? question in issue template.

Feel free to modify the issue template to update setup this workflow.

.github/workflows/issue-automation.yml Outdated

    
              on:

                issues:

                  types: [opened, edited, reopened, assigned, unassigned]

Collaborator

Avdhesh-Varshney Jan 24, 2026

Remove assigned and unassigned events

Avdhesh-Varshney assigned roshankumar0036singh

roshankumar0036singh force-pushed the feat/issue-automation branch from 647f72a to 4b30fb7 Compare

January 24, 2026 11:40

Contributor Author

roshankumar0036singh commented Jan 24, 2026

@Avdhesh-Varshney check now i have tried to use the os tracker but we need to test it one time as i cant test it locally

roshankumar0036singh force-pushed the feat/issue-automation branch from 4b30fb7 to 3fe26d3 Compare

January 24, 2026 11:46

Collaborator

Avdhesh-Varshney commented Jan 24, 2026

@roshankumar0036singh Your earlier contribution was awesome. Please keep the same consistency.
I've reviewed these updated changes. These all are written using AI and you have not gone through github project tracker at once.

Focus on quality contribution not on quantity. Please atleast read & review your code on your own first.
Later, I'll review and test the workflow.

Contributor Author

roshankumar0036singh commented Jan 25, 2026 •

edited

Loading

@Avdhesh-Varshney i worked on it but currently it is using the github token which normally cant wrtie to the organisation level project we might need to use pat

Collaborator

Avdhesh-Varshney commented Jan 25, 2026

@roshankumar0036singh pat? - personal token?

If personal token, do you say We need to write it hard-coded in workflow? or need to setup in settings?

Contributor Author

roshankumar0036singh commented Jan 25, 2026 •

edited

Loading

@Avdhesh-Varshney need to setup as a New repository secret in settings and whatever name you used for it give me that name

Contributor Author

roshankumar0036singh commented Jan 25, 2026

token is encrypted in GitHub's secret storage ,It's never visible in logs or code

Collaborator

Avdhesh-Varshney commented Jan 25, 2026

CODE_A2Z_ORG_FINE_GRAINED_PAT_FOR_ASSIGN_WORKFLOW

Contributor Author

roshankumar0036singh commented Jan 26, 2026

@Avdhesh-Varshney need this scopes for pat project , read and write and did you added it as a Repository Secret

Collaborator

Avdhesh-Varshney commented Jan 26, 2026

Addedas repository secret.
But wait confirming with project read and write permissions

roshankumar0036singh force-pushed the feat/issue-automation branch from 0270d15 to 6499989 Compare

January 26, 2026 16:04

roshankumar0036singh closed this

roshankumar0036singh force-pushed the feat/issue-automation branch from 6499989 to 219c683 Compare

January 26, 2026 16:06

roshankumar0036singh reopened this

Contributor Author

roshankumar0036singh commented Jan 26, 2026

@Avdhesh-Varshney check now there was slight issue this code formating issue if from earlier commit made to the code-a2z repo not by my commit

roshankumar0036singh added 2 commits

January 26, 2026 22:04


          feat: add comprehensive issue automation system

5131b4a

- Auto-assign issues when users select 'Yes' in issue form
- Support /assign command for manual assignment
- Enforce 2-issue limit per user
- Daily deadline checks with priority-based timeouts (3/6/8 days)
- Warning notifications 24h before deadline
- Project V2 integration with OS - TASK TRACKER
- Idempotent project sync with status updates
- Comprehensive error handling and logging
- Production-ready workflow with timeouts and concurrency control


          feat: add comprehensive issue automation system

ced2f15

- Auto-assign issues when users select 'Yes' in issue form
- Support /assign command for manual assignment
- Enforce 2-issue limit per user
- Daily deadline checks with priority-based timeouts (3/6/8 days)
- Warning notifications 24h before deadline
- Project V2 integration with OS - TASK TRACKER
- Idempotent project sync with status updates
- Comprehensive error handling and logging
- Production-ready workflow with timeouts and concurrency control

roshankumar0036singh force-pushed the feat/issue-automation branch from 087e2a7 to ced2f15 Compare

January 26, 2026 16:34

Collaborator

Avdhesh-Varshney commented Jan 26, 2026

@roshankumar0036singh Yes that was due to some earlier commits.
Leave that workflow check for this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet