Closed Kota-Karthik closed 2 weeks ago
Hello, I want to try working on this could you assign it to me. Please do add the labels of GSSoCc-ext and hacktoberfest-accepted.
@Chin-may02 can you explain your approach first? like how're you going to achieve this? and also @Kota-Karthik here you go.
I will update the flow to check the label and accurately identify them, assignment will only be done if they are not a collaborator
Do I create a new file or edit the existing one ?
@Chin-may02 edit the existing one
Sure will do, could you please add the level for this issue
Sorry to interrupt but could you please assign the level of this tsak
@Chin-may02 I will assign the level but before that , just lemme inform you , the changes you made doesn't fix the issue still the issues aare not being assigned automatically I hope you fix them correctly this time and make sure to check before making a new PR , as i closed the previous one!
Okay will try again
@Chin-may02 Just make sure to test the workflow correctly But this time i would need a screen recording showing that workflows work correctly!
@Chin-may02 Workflow is failing , please make sure everything works well before making a PR!
It isn't working I would like to step down
What workflow needs to be updated?
The auto-assign workflow that triggers when an issue is opened or reopened.
Describe the proposed changes
I propose the following changes to ensure the workflow functions correctly:
Motivation
The current workflow is not assigning issues as intended when they are created or reopened, which affects our issue management process. Having issues auto-assigned helps streamline our workflow, and ensuring they are unassigned after a week of inactivity helps keep our issue list manageable.
Additional context
I have already implemented the workflow, but it isn't functioning as expected. Changes need to be made in
.github/workflows/auto_assign_issues.yml
.Please test the changes before raising a PR and add screenshots for verification.