You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found this case only because of my plugin's tests fail after updating gradle-git-publish from 0.3.4 to 2.1.3. This is very minor.
The case: publishing site to github pages when a remote gh-pages branch does not exist.
First site publication (gitPublishPush):
gitPublishReset detects that remote gh-pages branch does not exist and creates orphan local branch gh-pages
gitPublishPush publish local branch, creating a remote branch
On the next publication, gitPublishReset already detects that remote for gh-pages exists, but it did not set tracking for the local branch! So the local branch remains orphan.
Of course, everything will work correctly (all subsequent publications).
It only affects UP_TO_DATE check for gitPublishPush as it will never be able to check the branch status: because the branch is orphan, gitPublishPush.onlyIf will never return false
My workaround (just in case) is to set tracking just after publication (groovy):
It would be great if the plugin would be able to detect the orphan branch automatically and update it's tracking (just after publication or in gitPublishReset (on next run)).
The text was updated successfully, but these errors were encountered:
I found this case only because of my plugin's tests fail after updating gradle-git-publish from 0.3.4 to 2.1.3. This is very minor.
The case: publishing site to github pages when a remote
gh-pages
branch does not exist.First site publication (gitPublishPush):
gitPublishReset
detects that remotegh-pages
branch does not exist and creates orphan local branchgh-pages
gitPublishPush
publish local branch, creating a remote branchOn the next publication,
gitPublishReset
already detects that remote forgh-pages
exists, but it did not set tracking for the local branch! So the local branch remains orphan.Of course, everything will work correctly (all subsequent publications).
It only affects UP_TO_DATE check for
gitPublishPush
as it will never be able to check the branch status: because the branch is orphan, gitPublishPush.onlyIf will never return falseMy workaround (just in case) is to set tracking just after publication (groovy):
It would be great if the plugin would be able to detect the orphan branch automatically and update it's tracking (just after publication or in gitPublishReset (on next run)).
The text was updated successfully, but these errors were encountered: