Skip to content

Conversation

@jdanieck
Copy link
Contributor

@jdanieck jdanieck commented May 21, 2025

Description

Added workflow to trigger dev artifacts push manually from Actions tab.

Once this is merged to main I'll test it via manual trigger (can't do it before the merge) and if it works I'll raise another PR to disable automatic push in pre-merge workflow.

Any Newly Introduced Dependencies

No.

How Has This Been Tested?

Triggered the workflow from current PR (then removed the trigger). Check this run.

image

Checklist:

  • I agree to use the APACHE-2.0 license for my code changes
  • I have not introduced any 3rd party dependency changes
  • I have performed a self-review of my code

@jdanieck jdanieck self-assigned this May 21, 2025
@jdanieck jdanieck marked this pull request as ready for review May 21, 2025 12:39
Copy link
Contributor

@jokuniew jokuniew left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To trigger a workflow in a repository, the user should be a collaborator with Write permission in the repository. Normally the external users can’t trigger workflows in the repository.
If the external users use a pull request to trigger workflow from the forked repository, the GITHUB_TOKEN only has read permissions for some scope.

https://github.com/orgs/community/discussions/26053
i hope we are protected enough from unathorized push
After this PR merge i'll try to validate it with private repo

@jdanieck jdanieck requested a review from cgoea May 21, 2025 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants