Jiang Xin <worldhello.net@xxxxxxxxx> writes: >> > One such solution could be to make the `git-po-helper` job contingent on >> > part of the repository name. For example: >> > >> > git-po-helper: >> > if: endsWith(github.repository, '/git-po') >> > [...] >> > >> > would skip the job unless the target repository's name is `git-po`. >> >> Nice. >> >> Can this be made into a matter purely local to git-l10n/git-po >> repository and not git/git repository? I am wondering if we can ee >> if the current repository is git-l10n/git-po or its fork and run it >> only if that is true. > > I have read almost all the github documents on github actions, and > tried to find if I can use a local branch, such as "github-action" to > hold local github-actions, but no locky. > > That is to say, the workflow file must be introduced to the master > branch of “git-l10n/git-po”. As "git-l10n/git-po" is a fork of > "git/git", the new workflow should be part of "git/git", and provide a > way to disable it by default. Yeah, that part I am agreeing with you. I was just wondering if we can do better than Dscho's heuristics (the repository name ending with /git-po) to catch git-l10n/git-po or its fork to enable the workflow in.
