capabilities.work

Feature Branch To Merged Pull Request

A 3-step recipe with Gitea. We can help you get access.

Recipe · 3 steps

Feature Branch To Merged Pull Request

with Gitea · Software Construction Management

Create a branch, open a pull request, and merge it.

  1. Create a new feature branch from the base branch.
  2. Open a pull request from the new feature branch into the base branch.
  3. Merge the pull request using the requested merge strategy.
What you'll need to have ready
  • authToken: Authorization header value, e.g. "token <personal-access-token>".
  • owner: Owner of the repository.
  • repo: Name of the repository.
  • newBranch: Name of the feature branch to create.
  • baseBranch: Existing branch the feature branch is created from and merged back into.
  • prTitle: Title of the pull request.
  • prBody: Description body for the pull request.
  • mergeStyle: Merge strategy (merge, rebase, rebase-merge, squash, fast-forward-only).
For your developer

Arazzo workflow gitea:branch-pull-request-merge, 3 operations: repoCreateBranch → repoCreatePullRequest → repoMergePullRequest. Specs on APIs.io.

More recipes with Gitea

Bootstrap Repository With Tracking IssueComment And Close IssueCommit File On New Branch And Open Pull RequestCreate Branch And Await AvailabilityDraft Then Publish ReleaseCreate Label And Apply To IssueCreate Milestone With Tracked IssueSync Mirror And Confirm BranchOpen And Triage Pull RequestBootstrap Organization With Shared Label