trstringer
Can't get the approval values
Please can someone explain me how can i get the approval values (yes, approve...) when i click on the approve and deploy button in the Review pending deployment pop up. I want to make some conditions with it in my following step but it doesn't work and i don't see any example about that in the docs. I got always a pending status in Manual Workflow Approval step before fail.
I am also facing the same issue
Hi @G-Gowtham Are you find a eventual solution ?
Sorry, I'm not understanding the problem. You can't find the approval keywords? Those are hardcoded.
@MamadouSadio @trstringer It seems I can't able to approve the request which is created by myself even though I am a assignee.
@MamadouSadio @trstringer It seems I can't able to approve the request which is created by myself even though I am a assignee.
I'm experiencing the same, can't seem to approve the workflow at all.
Were you guys able to figure out what the problem is? - The action opens the issue successfully for me - but it won't register when I comment a 'approve' or 'approved' keyword in order to continue the workflow, I've also set 'exclude-workflow-initiator-as-approver:' to false - but no luck.
So I figured out the reason was that I had set myself in the approvers field as 'velink' but it is case-sensitive so updating it to 'Velink' fixed it.
Huge thanks to the @trstringer for creating this - it will save me $100 a month not having to get GitHub Enterprise. The only feature my team required from Enterprise is the manual approval step to deploy to production, and we wouldn't have utilised any of the other features offered by Enterprise just had to pay for them which would have been a waste.
I want to make some conditions with it in my following step but it doesn't work and i don't see any example about that in the docs.
That's because this doesn't exist yet - I have a PR open that does this though! https://github.com/trstringer/manual-approval/pull/147
getting the same issue when I comment 'approve' or 'approved' keyword in order to continue the workflow. Is this will be resolved anytime soon ?
This issue was resolved on the code level in Feb, but the release was created in the last week of May, so now you shouldn't be experiencing the issue.
If you still face the issue, please open an issue again, closing this for now
