@DonnieBLT, I believe we need to make changes in the OWASP-BLT/BLT-Action repo to resolve this issue. However, I was hoping you could provide some guidance on how to approach this. Are there specific areas of the repo or existing functionalities that you think we should modify to implement the auto addition of $5 when posted by a user in the SPONSORS env?

for existing repos that are not BLT-Action we'd be adding a SPONSORS variable to the auto-assign yml - this can be updated in the Action readme

for existing repos that are not BLT-Action we'd be adding a SPONSORS variable to the auto-assign yml - this can be updated in the Action readme

@DonnieBLT Thanks for the guidance. I have a few clarification questions:

1. I don't see an existing auto-assign.yml file in either the OWASP/BLT or BLT-Action repositories. Should I create a new auto-assign.yml file to implement the SPONSORS variable, or should I modify another existing workflow file?

2. For the Action readme update, I understand you're referring to the README in the BLT-Action repository. Could you clarify what specific information should be added there? Should it document the new SPONSORS parameter, how to configure it, and its purpose?

I want to make sure I'm approaching this issue correctly and making changes in the right places. Any additional guidance would be greatly appreciated!

1. It’s in the .github folder
2. Yes one line to the readme

1. It’s in the .github folder
2. Yes one line to the readme

I think you're referring to the assign-issues.yml file in the .github/workflows folder. I have attached a screenshot of it here:

For the second point, I'll make the necessary addition to the README file in the BLT-Action repository to document the new SPONSORS variable functionality.

Ok yes

Ok yes

Got it, I'll work on the changes then. Thanks for confirming!

/assign

Hello @vidipsingh! You've been assigned to OWASP-BLT/BLT issue #3859. You have 24 hours to complete a pull request.

⏰ This issue has been automatically unassigned due to 24 hours of inactivity. The issue is now available for anyone to work on again.