Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: allow overriding source.path in remote actions (when using source.repository) #6750

Merged
merged 1 commit into from
Jan 9, 2025

Conversation

stefreak
Copy link
Member

@stefreak stefreak commented Jan 7, 2025

What this PR does / why we need it:
Allow overriding source.path in remote actions (when using source.repository).

This is useful when an action source path needs to be a subdirectory in a remote repository.

Special notes for your reviewer:
This feature already was working, I just lifted the limitation in the validation code and added a test, and updated docs.

See also Discord thread: https://discord.com/channels/817392104711651328/1320775997880144005/1320775997880144005

@stefreak stefreak force-pushed the feat-remote-action-path branch 2 times, most recently from ca72612 to a6bcbec Compare January 7, 2025 14:46
Copy link
Collaborator

@twelvemo twelvemo left a comment

Choose a reason for hiding this comment

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

Looks good! Just one tiny nit on a sentence in the docs.

@@ -44,11 +44,9 @@ A description of the action.

By default, the directory where the action is defined is used as the source for the build context.

You can override this by setting either `source.path` to another (POSIX-style) path relative to the action source directory, or `source.repository` to get the source from an external repository.
You can override directory that is used for the build context by setting `source.path`.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
You can override directory that is used for the build context by setting `source.path`.
You can override the directory that is used for the build context by setting `source.path`.

Copy link
Member Author

@stefreak stefreak Jan 8, 2025

Choose a reason for hiding this comment

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

Thank you for spotting this, I have applied your suggestion ✅

@stefreak stefreak force-pushed the feat-remote-action-path branch from a6bcbec to dbb75e2 Compare January 8, 2025 09:42
@stefreak stefreak requested a review from twelvemo January 8, 2025 09:42
@stefreak stefreak enabled auto-merge January 8, 2025 13:28
@stefreak stefreak added this pull request to the merge queue Jan 8, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 8, 2025
@stefreak stefreak added this pull request to the merge queue Jan 8, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 8, 2025
@twelvemo twelvemo added this pull request to the merge queue Jan 8, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 8, 2025
@vvagaytsev vvagaytsev added this pull request to the merge queue Jan 9, 2025
Merged via the queue into main with commit 20a4ba3 Jan 9, 2025
42 checks passed
@vvagaytsev vvagaytsev deleted the feat-remote-action-path branch January 9, 2025 09:27
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.

3 participants