Skip to content

Bug: PR workflow does not work as expected for PRs from fork repositories #182

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.

Sign up for GitHub

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

Jump to bottom
Closed
1 task done
OptimumCode opened this issue Aug 5, 2024 · 0 comments · Fixed by #184
Closed
1 task done

Bug: PR workflow does not work as expected for PRs from fork repositories #182

OptimumCode opened this issue Aug 5, 2024 · 0 comments · Fixed by #184
Assignees
@OptimumCode
Labels
bug Something isn't working CI/CD

Comments

@OptimumCode
Copy link
Owner

OptimumCode commented Aug 5, 2024 •
edited
Loading

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

There are several issues:

  • danger check does not have permissions to leave a comment on PR
  • review-dog doesn’t add comments for issues
  • FOSSA workflow publishes the results for a wrong repository

Expected Behavior

All workflows must work the same way for PRs from forks as they work when a PR is done from this repo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@OptimumCode OptimumCode

Labels
bug Something isn't working CI/CD
Projects
Multi-platform JSON schema validator
Status: ✅ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Correct PR workflow to work for PRs from forked repositories OptimumCode/json-schema-validator
1 participant
@OptimumCode