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.

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

scm_folder docs #3218

Merged
merged 1 commit into from
May 17, 2023
Merged

scm_folder docs #3218

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
12 changes: 9 additions & 3 deletions reference/conanfile/attributes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,12 +79,18 @@ revision_mode
-------------

This attribute allow each recipe to declare how the revision for the recipe itself should
be computed. It can take two different values:
be computed. It can take three different values:

- ``"hash"`` (by default): Conan will use the checksum hash of the recipe manifest to
compute the revision for the recipe.
- ``"scm"``: the commit ID will be used as the recipe revision if it belongs to a known
repository system (Git or SVN). If there is no repository it will raise an error.
- ``"scm"``: if the project is inside a Git repository the commit ID will be used as the
recipe revision. If there is no repository it will raise an error.
- ``"scm_folder"``: This configuration applies when you have a mono-repository project, but
still want to use *scm* revisions. In this scenario, the revision of the exported
`conanfile.py` will correspond to the commit ID of the folder where it's located. This
approach allows multiple `conanfile.py` files to exist within the same Git repository,
with each file exported under its distinct revision.



upload_policy
Expand Down