-
Notifications
You must be signed in to change notification settings - Fork 719
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
Addition of listCodeownersErrors() #1597
Comments
The test repository does not have a |
Add the file, that seems fine. |
I just tried, and got 403 Forbidden. Could you either give me permission, or yourself add the file containing the following single line? |
I've invited you to the |
…istCodeownersErrors Issue #1597: Add deliberately broken CODEOWNERS file
@bitwiseman the PR #1604, for this issue, closed the PR #1579 instead of issue #1579 (same number). The PR #1579 addresses issue #1549. Wich now has a automatically closed PR with good fix (opiniated). Please close this issue as it it addressed by #1604. |
Sorry about the confusion between pull request and issue numbers; this seems to derive from the instructions when opening a pull request 'If this PR fixes one or more issues, include "Fixes #" lines for each issue."' But "#" causes GitHub to introduce a link to the appropriately-numbered pull request, not issue. I suggest you modify the instructions for pull requests. @robinvandenbogaard: FYI, this issue is not yet ready to be closed; it requires two pull requests, only one of which has been submitted so far. |
I don't quite understand how my pull request in Anyhow, I have now tested and implemented my change, and recorded a Wiremock snapshot of the data. Now I just need permission to push to |
I merged it by mistake. You shouldn't need more permissions to submit a PR for your feature to |
Fair enough. I'm not used to working with forks in this way. |
I have created a pull request now. Note that there seems to be a general problem in the tests (meaning I could replicate it with a test other than the one I created for my code, by temporarily deleting the Wiremock data), which seems to be the result of the JSON returned by fetching the repository being truncated, and hence not valid JSON. This problem is intermittent, but occurs most of the time; since, however, it is out of the scope of this issue, I have not endeavoured to fix it. Here is a stack trace, should you find it helpful:
|
Hello. Without wanting to chivvy you, could I remind you that pull request #1610 has been awaiting your approval for the last two weeks, just in case it had slipped off your radar. |
I would like to contribute a method offering access to the GitHub API call
/repos/{owner}/{repo}/codeowners/errors
.The text was updated successfully, but these errors were encountered: