Add option to delete branch after pr got merged #929

Describe what your pull request does and which issue you’re targeting

Closes #860

I carefully read the contribution guidelines.
I'm following the code standards as defined here.
By submitting this pull request, I permit GitNex to license my work under the GNU General Public License v3.

(Just FYI this is and was already ready for review)

@qwerty287 Here are some imprvoments to be made after my initial review:

Create an Action class in actions package with a name PullRequestActions.
Move all the logic from Bottomsheet to PullRequestActions.

Here are some examples:

Action class method

Calling action class method from bottomsheet

Create an Action class in actions package with a name PullRequestActions.

You could also just create a ViewModel.

I moved the delete branch method to the pull request actions class, but I can't move more things. Most of the actions aren't pr-specific and also moved to the IssueActions.

Btw, maybe you know it already, but the CI actions always fail

Running with gitlab-runner 13.12.0-rc1 (b21d5c5b)
  on docker-auto-scale 72989761
  feature flags: FF_GITLAB_REGISTRY_HELPER_IMAGE:true, FF_SKIP_DOCKER_MACHINE_PROVISION_ON_CREATION_FAILURE:true
Resolving secrets 00:00
Preparing the "docker+machine" executor 00:07
Using Docker executor with image curlimages/curl:7.76.1 ...
Pulling docker image curlimages/curl:7.76.1 ...
Using docker image sha256:bbadf782a297d4373dc4efd44b7877040b75e661e44adca59595c9148adc6f81 for curlimages/curl:7.76.1 with digest curlimages/curl@sha256:fa32ef426092b88ee0b569d6f81ab0203ee527692a94ec2e6ceb2fd0b6b2755c ...
Preparing environment 00:01
Running on runner-72989761-project-19824009-concurrent-0 via runner-72989761-srm-1623008112-6c1fad81...
Getting source from Git repository 00:02
$ eval "$CI_PRE_CLONE_SCRIPT"
Fetching changes with git depth set to 50...
Initialized empty Git repository in /builds/opyale/gitnex/.git/
Created fresh repository.
Checking out 0fc845e0 as main...
Skipping Git submodules setup
Executing "step_script" stage of the job script 00:01
Using docker image sha256:bbadf782a297d4373dc4efd44b7877040b75e661e44adca59595c9148adc6f81 for curlimages/curl:7.76.1 with digest curlimages/curl@sha256:fa32ef426092b88ee0b569d6f81ab0203ee527692a94ec2e6ceb2fd0b6b2755c ...
$ ./scripts/add-commit-status.sh
sh: eval: line 121: ./scripts/add-commit-status.sh: not found
Cleaning up file based variables 00:00
ERROR: Job failed: exit code 127

e.g. https://gitlab.com/opyale/gitnex/-/jobs/1322447387

I found two settings string arrays (cache size) that aren't in the settings.xml, is it ok if I push them into this branch/pr?

Sure, go ahead.

Btw, maybe you know it already, but the CI actions always fail

Yes, don't worry, I will fix it soon. 🙂

 import org.mian.gitnex.helpers.Toasty;
 import retrofit2.Call;
 import retrofit2.Callback;


				`public class PullRequestActions {`

				`public static void deleteHeadBranch(@NonNull Context context, String repoOwner, String repoName, String headBranch, boolean showToasts) {`

 				.getApiInterface(context)
 				.deleteBranch(Authorization.get(context), repoOwner, repoName, headBranch);
 			call.enqueue(new Callback<JsonElement>() {

 				public void onFailure(@NonNull Call<JsonElement> call, @NonNull Throwable t) {
 					if(showToasts) Toasty.error(context, context.getString(R.string.deleteBranchError));
 					Log.i("onFailure", t.toString());


				`}`

				`private void deleteBranchFunction(String repoOwner, String repoName) {`


				`deletePullRequestBranch.setOnClickListener(v -> {`

				`assert ctx != null;`

Add option to delete branch after pr got merged #929

Describe what your pull request does and which issue you’re targeting

Reviewers