-
Notifications
You must be signed in to change notification settings - Fork 1
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.
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
refactor/feat rewrite action and add new commands #245
Conversation
I tested the branch. Output of GitHub:
The new placeholders don't seem to work:
|
Action always adds a comment - even if no assign command is used: |
I failed making it work on the first try π€£π€£ Well, thanks for testing this out. I still have failing tests that needs to be fixed that's why I haven't tested this yet on my Will try to make it work tomorrow morning π |
Tested
|
It will work if this pr is merged and I'm working on it. Just needs to do some final testing and update the readme |
I am just impatient π π€£π€£ |
Thanks so much @koppor for all the issues you opened this week and for your patience throughout the process. Your detailed descriptions were incredibly helpful! It made me really happy to work on this again after 2 years π If you encounter any more issues or have ideas for new features within the action, donβt hesitate to open more issues. Your contributions are greatly appreciated! π |
What type of PR is this? (check all applicable)
Description
This pr adds new commands to the action.
Features
/assign @<user>
&/unassign @<user>
commands used by maintainers to assign and unassign issues to contributors/assign-me
&/unassign-me
commands are for contributors wanting to take on an issueRelated Tickets & Documents
unassigned_comment
Β #244/assign-previous-commenter
Β #240/unassign-me
and/unassign-previous-commenter
Β #241Mobile & Desktop Screenshots/Recordings
Added tests?
Added to documentation?
[optional] What gif best describes this PR or how it makes you feel?