Add fork branch sync

[jonesbusy]

Description

Add support for fork sync branch

Fixing https://github.com/hub4j/github-api/issues/1626

Added two wiremock test and tested a SNAPSHOT version in a WIP PR https://github.com/jenkinsci/plugin-modernizer-tool/pull/141

I confirm this work by enabling logs and ensuring my fork is sync directly on GitHub

(e24ddd0) GitHub API request: POST https://api.github.com/repos/jonesbusy/jobcacher-plugin/merge-upstream 

Before submitting a PR:

• [x] Changes must not break binary backwards compatibility. If you are unclear on how to make the change you think is needed while maintaining backward compatibility, CONTRIBUTING.md for details.
• [x] Add JavaDocs and other comments explaining the behavior.
• [x] When adding or updating methods that fetch entities, add @link JavaDoc entries to the relevant documentation on https://docs.github.com/en/rest .
• [x] Add tests that cover any added or changed code. This generally requires capturing snapshot test data. See CONTRIBUTING.md for details.
• [x] Run mvn -D enable-ci clean install site locally. If this command doesn't succeed, your change will not pass CI.
• [x] Push your changes to a branch other than main. You will create your PR from that branch.

When creating a PR:

• [x] Fill in the "Description" above with clear summary of the changes. This includes:
• [x] If this PR fixes one or more issues, include "Fixes #" lines for each issue.
• [x] Provide links to relevant documentation on https://docs.github.com/en/rest where possible. If not including links, explain why not.
  • [x] All lines of new code should be covered by tests as reported by code coverage. Any lines that are not covered must have PR comments explaining why they cannot be covered. For example, "Reaching this particular exception is hard and is not a particular common scenario."
  • [x] Enable "Allow edits from maintainers".

API is https://docs.github.com/en/rest/branches/branches?apiVersion=2022-11-28#sync-a-fork-branch-with-the-upstream-repository

Code is covered 100%

[codecov[bot]]

Codecov Report

Attention: Patch coverage is 92.85714% with 1 line in your changes missing coverage. Please review.

Project coverage is 81.32%. Comparing base (3c4d80c) to head (6493b2c).

Files	Patch %	Lines
src/main/java/org/kohsuke/github/GHBranchSync.java	87.50%	1 Missing :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #1898 +/- ## ============================================ + Coverage 81.29% 81.32% +0.02% - Complexity 2450 2457 +7 ============================================ Files 238 239 +1 Lines 7449 7463 +14 Branches 400 400 ============================================ + Hits 6056 6069 +13 - Misses 1146 1147 +1 Partials 247 247 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[jonesbusy]

Sure thanks, I will try to add a new model for the sync response and perform some assertion on it

[jonesbusy]

I've added the GHBranchSync model and return it

I've also added a negative test when the API return a non-200 status code (for example 422 when the repo is not a fork)

[jonesbusy]

Apparently something wrong with javadoc. I will take a look

[jonesbusy]

Should be fixed, can you restart the workflows please ?

[jonesbusy]

Hi @bitwiseman Sorry for the ping, but where you able to review again this PR ?

It's also update with the default branch

Thanks!

[jonesbusy]

Thanks for the merge @bitwiseman. Sorry to ping you directly (again) but is there a release soon including this feature ?

I'm asking because we are approaching the end of the Google Summer of Code on our project https://github.com/jenkinsci/plugin-modernizer-tool and would be great that we can include the new release on our delivery

The fork sync is quiet critical on our project to avoid opening PRs from outdated forks.

Thanks for your consideration 😃

[bitwiseman]

I'll do a release today.