Skip branch setup on publish

[jtpio]

Publishing a release seems to be failing on repos with a default branch not named master at the forwardport-changelog step.

Example run for a repo with main as the default branch: https://github.com/jtpio/jupyter_releaser/runs/3951643392?check_suite_focus=true

Comparing this workflow:

To a previous successful one:

We see the releaser used to run git remote show origin first to retrieve the default branch.

Which seems to indicate that it was defaulting to:

jupyter_releaser/jupyter_releaser/util.py

Lines 123 to 128 in 6dd044a

	def get_default_branch():
	"""Get the default remote branch"""
	info = run("git remote show origin")
	for line in info.splitlines():
	if line.strip().startswith("HEAD branch:"):
	return line.strip().split()[-1]

Here:

jupyter_releaser/jupyter_releaser/lib.py

Line 581 in 6dd044a

branch = branch or util.get_default_branch()

Probably the branch was previously not passed down to forwardport_changelog (empty).

This PR removes the RH_BRANCH override which should revert back to the previous behavior (not tested yet)

[codecov-commenter]

Codecov Report

Merging #192 (da6f240) into master (6dd044a) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master     #192   +/-   ##
=======================================
  Coverage   84.77%   84.77%           
=======================================
  Files          19       19           
  Lines        2273     2273           
  Branches      280      280           
=======================================
  Hits         1927     1927           
  Misses        250      250           
  Partials       96       96           

Impacted Files	Coverage Δ
jupyter_releaser/actions/publish_release.py	0.00% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6dd044a...da6f240. Read the comment docs.

[blink1073]

Thanks!

[jtpio]

Ah that might not be enough for the Full Release workflow, as the common setup is also invoked here

jupyter_releaser/.github/workflows/full-release.yml

Lines 41 to 42 in 6dd044a

	- name: Setup
	uses: ./.github/actions/common

Edit: never mind this should actually not be related.

[jtpio]

Ah still seeing this issue with the Full Release workflow after syncing the fork with the latest: https://github.com/jtpio/jupyter_releaser/runs/3973150079?check_suite_focus=true

[jtpio]

COMMAND: jupyter-releaser forwardport-changelog https://github.com/jupyterlite/xeus-lua-kernel/releases/tag/untagged-db12667508940e81849a --branch master

According to the logs it used master as the default branch so it probably picked it up from the jupyter_releaser repo.