.forceignore v2 warning when ignoring **/README.md
See original GitHub issueSummary
.forceignore v2 warning when ignoring **/README.md
Received this warning when trying to run force:source:push, the push is successful I just get a warning.
(node:3085) Warning: The .forceignore file doesn't adhere to .gitignore format which will be the default behavior starting in Spring '21 release. More information on .gitignore format here: https://git-scm.com/docs/gitignore. Fix the following lines in your .forceignore and add '# .forceignore v2' to your .forceignore file to switch to the new behavior. (Use
node --trace-warnings … to show where the warning was created) (node:3085) Warning: **/README.md
The ignore pattern in use was to ignore all README.md files in all dirs.
Steps To Reproduce:
- Create a project with a README.md file
- Add
**/README.md
to.forceignore
- Use
force:source:push
- You will get the error
Expected result
Seem like it is a valid ignore pattern based on git ignore, so no warning should be seen.
Actual result
I get this error instead.
(node:3085) Warning: The .forceignore file doesn't adhere to .gitignore format which will be the default behavior starting in Spring '21 release. More information on .gitignore format here: https://git-scm.com/docs/gitignore. Fix the following lines in your .forceignore and add '# .forceignore v2' to your .forceignore file to switch to the new behavior. (Use
node --trace-warnings … to show where the warning was created) (node:3085) Warning: **/README.md
SFDX CLI Version(to find the version of the CLI engine run sfdx --version):
SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core)
OS and version: MacOS Big Sur: 11.2 (20D64)
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (1 by maintainers)
@mshanemc I am also facing this issue while adding a
README.md
file toforceIgnore
.Below are the lines which are triggering the warning:
The output of sfdx plugins:
And the output of sfdx --version:
The lines seem to be adhering the gitignore format as mentioned by @lukecotter, so no apparent reason for the warning message to appear.
I still see the warning when pushing, the push works though. forceignore is set to v2.
here is the warning on latest cli
and the versions