[action]Adds action for obtaining remote repo default branch

[seanmcneil]

Checklist

• I've run bundle exec rspec from the root directory to see all new and existing tests pass
• I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
• I've read the Contribution Guidelines
• I've updated the documentation if necessary.

Motivation and Context

This introduces a new action to obtain the default branch name from a remote git repository. Doing this can support other actions such as creating merge requests by ensuring that the proper branch name is provided as a target. With the shift away from "master", it is beneficial to have this kind of flexibility.

Description

A new action has been created in the source control category that enables retrieving a remote git repository's default branch.

It was tested under the following conditions:

• In a folder with no available git repo (an empty string was returned)
• In a folder with a git repo, but no available remote (an empty string was returned)
• In a folder with a valid git repo and the local branch on the default remote (correct branch name returned)
• In a folder with a valid git repo and the local branch NOT on the default remote (correct branch name returned)

Testing Steps

• Scenario 1, test in a folder with no git repo. Run bundle exec fastlane run git_default_remote_branch
• Scenario 2, test in a folder only a local git repo.
  • Init a git repo, commit a file
  • Run bundle exec fastlane run git_default_remote_branch
• Scenario 3, test in a folder with a valid remote repo
  • Clone a repo, ensure you are on the default branch
  • Run bundle exec fastlane run git_default_remote_branch . Default name should be seen
• Scenario 4, test in a folder with a valid remote repo while not on default branch
  • Clone a repo, switch to a non-default branch
  • Run bundle exec fastlane run git_default_remote_branch . Default name should be seen

[joshdholtz]

This looks great! I totes see a need for this. Just got two small requests 💪

[crazymanish]

This looks good to me, one minor suggestion if you agree! 🚀

[seanmcneil]

@joshdholtz Can you please check on your change request?

[google-cla]

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

[joshdholtz]

@googlebot I consent.

[joshdholtz]

This is great! Thank you so much for adding that remote_name option 🙌 I added one commit to clean up some syntax but other than that this is 💯 Really appreciate this ❤️

[fastlane-bot]

Congratulations! 🎉 This was released as part of fastlane 2.186.0 🚀