Can only specify existing branches for gh pages deployment

[eclipse-csi-bot]

In GitLab by @netomi on Aug 3, 2023, 20:05

When selecting legacy build type with a given deploy branch for GH pages, if the branch does not exist, GitHub will return an error.
This is consistent with the Web UI, where you can only select existing branches, however if would be useful if we can even specify non-existant branches as during validation we do know if the branch already exists.

One idea could be that we would create the branch if it does not exist yet, or enhance the validation to retrieve existing branches for the repo.

[eclipse-csi-bot]

In GitLab by @netomi on Aug 4, 2023, 10:09

It looks like you can specify non-existing branches, but only when gh pages have been activated before.
A workaround would be to enable it first with the main branch and then change the branch.

[eclipse-csi-bot]

In GitLab by @netomi on Aug 4, 2023, 11:06

mentioned in commit 852fa31

[eclipse-csi-bot]

In GitLab by @netomi on Aug 4, 2023, 11:11

Fixed by setting to an existing branch first and setting afterwards to the configured branch. That works with the GitHub api.