-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
API to GET all changed files in Pull Request #654
Comments
Is anyone currently working on this? If not I'd be happy to take a look |
@awwalker Please send a PR. |
Hi, any news with this feature? |
@romanresh @lunny Sorry I haven't had time to work on this recently. Once school slows down again I may have time to revisit it but for now I won't be active on this. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
😉 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
😉😉 |
Was this ever implemented? |
Not yet. |
I see in the docs: https://developer.github.com/v3/pulls/#list-pull-requests-files |
In my case, being able to get the list of modified files will enable putting multiples micro-services in a single "mono-repo" on Gitea (one per folder), and still be able to handle CI/CD independently for each of the micro-services. |
I'm in the same boat as @waterdrop01. I'm going to kludge my way around this, but an API in Gitea would enable a proper Drone extension to provide much cleaner integration. Edit: Though for the monorepo use case, we would also need an API to compare between two commits, for pushes. Looks like #11187 was abandoned. |
Make API for listing all changed files from a merge request like in GitHub:
https://developer.github.com/v3/pulls/#list-pull-requests-files
GET /repos/:owner/:repo/pulls/:number/files
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: