"I've manually triggered the git actions since I saw it was triggered by
merge" --> "I've manually triggered the git actions since I saw it was *NOT*
triggered by merge."
On Mon, Feb 7, 2022 at 9:33 PM tzach solomon
wrote:
> Daniel, you are correct.
> I've manually triggered the git actions
Daniel, you are correct.
I've manually triggered the git actions since I saw it was triggered by
merge.
The trigger was #27
https://github.com/jenkinsci/bitbucket-plugin/actions/runs/1795360127
What have I done wrong? I thought that by merging my PR it would auto
trigger the actions.
Thanks,
Hello Tim,
This (github invite) is probably something I could add to the plugin
adoption guideline.
I don't remember exactly at what moment, to achieve what, and under what
conditions it happens. It has been some time for me and I am not sure
anymore. Could you refresh my memory or point me
The release does not exist in the Maven repo, so it cannot be made
available.
Release drafter says the release was created from GH actions, but I cannot
find the CD run creating it. Timing-wise it should probably be between 42
and 41.
Any idea why some runs are attributed to the ghost user?
--
