Skip to content

Document what paths field does #1032

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.

Sign up for GitHub

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

Open
LecrisUT wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Document what paths field does #1032

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a450487
Remove the note that `paths` is only valid in `packages`
LecrisUT Apr 16, 2025
873a505
Document what `paths` does
LecrisUT Apr 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/configuration/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,11 @@ files_to_sync:
#### paths
(*list*) List of relative paths in the upstream repository, which should be considered for the particular package
(used mainly for monorepositories). Defaults to the root of the repository (`["./"]`).
This is the only key that can appear only inside [`packages`](#packages) dictionary values.

The first item of the list changes the working directory from which `specfile_path` is calculated and where other
actions and commands are run from.

Other entries in this field list have no effect currently.

#### specfile_path

Expand Down
Loading