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
The Cloudogu EcoSystem also supports Mercurial (and is develop on mercurial itself), so we should also support mercurial (aka hg).
A quick search reveals at least these two Git-specific implementations that must be generalized (e.g. using a SCM class, that can detect the remote somehow):
findEmailRecipients
SonarQube - sets the target branch to master (which is default on hg)
SonarCloud - uses Git class for BitBucket, which could be hg
Right now, the implementation is Git-only.
The Cloudogu EcoSystem also supports Mercurial (and is develop on mercurial itself), so we should also support mercurial (aka hg).
A quick search reveals at least these two Git-specific implementations that must be generalized (e.g. using a
SCM
class, that can detect the remote somehow):findEmailRecipients
SonarQube
- sets the target branch tomaster
(which isdefault
on hg)SonarCloud
- uses Git class for BitBucket, which could be hgNote:
getRepositoryUrl
:hg paths default
getCommitAuthorComplete
:hg log --branch . --limit 1 --template '{author}'
The text was updated successfully, but these errors were encountered: