-
Notifications
You must be signed in to change notification settings - Fork 29
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
feat: disable permit gen for users in non collaborative issues #182
feat: disable permit gen for users in non collaborative issues #182
Conversation
Please post QA and prove it works as expected |
Currently out for an university, will qa this issue in a few hours |
Qa is in progress please wait |
everything has been a mess since this pr got merged, tests not working resulting to it become weirdly hard to debug code |
ishowvel-org/.ubiquity-os#16 when issue closer is admin |
i hope for the tests to get fixed as this has caused me a magnitude of problems and headaches, waiting for workflows to run is not a good alternative to local test runs |
@0x4007 posted qa |
@gentlementlegen They claim your changes made this harder to test so you'll know best |
@ishowvel You can just merge the development branch here and you should not have any issues with the tests. |
test and qa both are passing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems close but study the code elsewhere to see how we do logging and comments. They are formatted using our logger methods.
@ishowvel please delete the |
this is just a one time failure because tests pass locally and this should get fixed if the workflow is ran once again |
@ishowvel I restarted the Jest site and indeed tests work. However, when I re-opened and closed an issue within an organization where I am an administrator, it didn't work, see Meniole#33 (comment) did you test this case? |
ishowvel-org/.ubiquity-os#39 (At the time of closing the issue ishowvel2 was admin, ishowvel2 is now a member) |
Here's the workflow run for this reward and the commit https://github.com/ishowvel/text-conversation-rewards/actions/runs/12046833453 |
@gentlementlegen can you give me the commit of the workflow run which produced that reward so I can debug further |
@ishowvel I am not sure about what you're asking me exactly, the workflow run url? If so, I ran that locally on my machine. Otherwise, the commit is the latest on your branch. |
@gentlementlegen things work on my end |
@gentlementlegen |
@ubiquity-ubiquibot is indeed a collaborator which is why it should fail, that worked fine. By my account is the admin of the org so I should have the capability to generate permits, which didn't work. |
admin the problem was me assuming that people will always follow the devflow of filing an issue, pricing the issue, assigning themselves and then closing |
@gentlementlegen https://github.com/ishowvel/text-conversation-rewards/actions/runs/12097760718/job/33733486500 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
_isCollaborative
, _nonAssigneeApprovedReviews
and _isAdmin
are duplicated. Please move these into another file and reuse them. Otherwise it seems to work fine now.
Seems ok |
I hate you mr GitHub actions |
6fbddbb
into
ubiquity-os-marketplace:development
Resolves #160