PaloAltoNetworks / PaloAltoNetworks/pan.dev
Issue/Help with "Get Repositories Blame Authors"
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 78
- Forks
- 88
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 18
Description
Documentation link
(https://pan.dev/prisma-cloud/api/code/get-blame-authors/)
Endpoint: https://api.prismacloud.io/api/v2/git/blameAuthors
Describe the problem
Is this endpoint currently accessible?
I assume this is the replacement for the now deprecated endpoint found here:
https://pan.dev/prisma-cloud/api/code/get-git-blame-authors/
Endpoint: https://api.prismacloud.io/code/api/v1/errors/gitBlameAuthors
While trying to access the new endpoint I am receiving a 404 Not Found response, whilst i can still reach the deprecated endpoint just fine.
Otherwise, is it possible that this endpoint URL is documented incorrectly?
https://api.prismacloud.io/api/v2/git/blameAuthors returns a 404
while
https://api.prismacloud.io/code/api/v2/git/blameAuthors returns a 403
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the documented Prisma Cloud Code API pages and compare the listed /api/v2/git/blameAuthors and /code/api/v2/git/blameAuthors endpoints with the deprecated endpoint described in the issue. Done means the documentation accurately identifies the endpoint URL and its availability or clearly explains the observed responses.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100