conan export . hello/0.1@demo/testing hello/0.1@demo/testing: WARN: There are uncommitted changes, skipping the replacement␣ ˓→of 'scm.url' and 'scm.revision' auto fields. Use --ignore-dirty to force it fields won’t be replaced unless you specify --ignore-dirty, and by default, the conan upload will block the upload of the recipe. This prevents recipes to be uploaded with incorrect scm values exported conanfile.txt. If you’d prefer to manually add the variables for each dependency, you can do so by skipping the CONFIG statement and only including conanbuildinfo.pri: Listing 12: yourproject.pro # ...

conan export . hello/0.1@demo/testing hello/0.1@demo/testing: WARN: There are uncommitted changes, skipping the replacement␣ ˓→of 'scm.url' and 'scm.revision' auto fields. Use --ignore-dirty to force it fields won’t be replaced unless you specify --ignore-dirty, and by default, the conan upload will block the upload of the recipe. This prevents recipes to be uploaded with incorrect scm values exported conanfile.txt. If you’d prefer to manually add the variables for each dependency, you can do so by skipping the CONFIG statement and only including conanbuildinfo.pri: Listing 12: yourproject.pro # ...

conan export . hello/0.1@demo/testing hello/0.1@demo/testing: WARN: There are uncommitted changes, skipping the replacement␣ ˓→of 'scm.url' and 'scm.revision' auto fields. Use --ignore-dirty to force it fields won’t be replaced unless you specify --ignore-dirty, and by default, the conan upload will block the upload of the recipe. This prevents recipes to be uploaded with incorrect scm values exported conanfile.txt. If you’d prefer to manually add the variables for each dependency, you can do so by skipping the CONFIG statement and only including conanbuildinfo.pri: Listing 12: yourproject.pro # ...

conan export . hello/0.1@demo/testing hello/0.1@demo/testing: WARN: There are uncommitted changes, skipping the replacement␣ ˓→of 'scm.url' and 'scm.revision' auto fields. Use --ignore-dirty to force it fields won’t be replaced unless you specify --ignore-dirty, and by default, the conan upload will block the upload of the recipe. This prevents recipes to be uploaded with incorrect scm values exported conanfile.txt. If you’d prefer to manually add the variables for each dependency, you can do so by skipping the CONFIG statement and only including conanbuildinfo.pri: Listing 12: yourproject.pro # ...

conan export . hello/0.1@demo/testing hello/0.1@demo/testing: WARN: There are uncommitted changes, skipping the replacement␣ ˓→of 'scm.url' and 'scm.revision' auto fields. Use --ignore-dirty to force it fields won’t be replaced unless you specify --ignore-dirty, and by default, the conan upload will block the upload of the recipe. This prevents recipes to be uploaded with incorrect scm values exported conanfile.txt. If you’d prefer to manually add the variables for each dependency, you can do so by skipping the CONFIG statement and only including conanbuildinfo.pri: Listing 12: yourproject.pro # ...

conan export . hello/0.1@demo/testing hello/0.1@demo/testing: WARN: There are uncommitted changes, skipping the replacement␣ ˓→of 'scm.url' and 'scm.revision' auto fields. Use --ignore-dirty to force it fields won’t be replaced unless you specify --ignore-dirty, and by default, the conan upload will block the upload of the recipe. This prevents recipes to be uploaded with incorrect scm values exported conanfile.txt. If you’d prefer to manually add the variables for each dependency, you can do so by skipping the CONFIG statement and only including conanbuildinfo.pri: Listing 12: yourproject.pro # ...

conan export . hello/0.1@demo/testing hello/0.1@demo/testing: WARN: There are uncommitted changes, skipping the replacement␣ ˓→of 'scm.url' and 'scm.revision' auto fields. Use --ignore-dirty to force it fields won’t be replaced unless you specify --ignore-dirty, and by default, the conan upload will block the upload of the recipe. This prevents recipes to be uploaded with incorrect scm values exported conanfile.txt. If you’d prefer to manually add the variables for each dependency, you can do so by skipping the CONFIG statement and only including conanbuildinfo.pri: Listing 12: yourproject.pro # ...

conan export . hello/0.1@demo/testing hello/0.1@demo/testing: WARN: There are uncommitted changes, skipping the replacement␣ ˓→of 'scm.url' and 'scm.revision' auto fields. Use --ignore-dirty to force it fields won’t be replaced unless you specify --ignore-dirty, and by default, the conan upload will block the upload of the recipe. This prevents recipes to be uploaded with incorrect scm values exported conanfile.txt. If you’d prefer to manually add the variables for each dependency, you can do so by skipping the CONFIG statement and only including conanbuildinfo.pri: Listing 12: yourproject.pro # ...

conan export . hello/0.1@demo/testing hello/0.1@demo/testing: WARN: There are uncommitted changes, skipping the replacement␣ ˓→of 'scm.url' and 'scm.revision' auto fields. Use --ignore-dirty to force it fields won’t be replaced unless you specify --ignore-dirty, and by default, the conan upload will block the upload of the recipe. This prevents recipes to be uploaded with incorrect scm values exported conanfile.txt. If you’d prefer to manually add the variables for each dependency, you can do so by skipping the CONFIG statement and only including conanbuildinfo.pri: Listing 12: yourproject.pro # ...

conan export . hello/0.1@demo/testing hello/0.1@demo/testing: WARN: There are uncommitted changes, skipping the replacement␣ ˓→of 'scm.url' and 'scm.revision' auto fields. Use --ignore-dirty to force it fields won’t be replaced unless you specify --ignore-dirty, and by default, the conan upload will block the upload of the recipe. This prevents recipes to be uploaded with incorrect scm values exported conanfile.txt. If you’d prefer to manually add the variables for each dependency, you can do so by skipping the CONFIG statement and only including conanbuildinfo.pri: Listing 12: yourproject.pro # ...