.forceignore **.md bug
See original GitHub issueSummary
Following this guide on excluding files when syncing or pushing to a scratch org I implemented **.md
in my .forceignore
.
Vivek also includes this notation in his template repo’s forceignore.
There is an issue with the way sfdx is handling **.md
in the forceignore and custom metadata when pushing to the org. If you have a customMetadata file named MyCustomMetadata.md-meta.xml, this will be ignored.
Steps To Reproduce:
- Step 1. Have a custom metadata file in your source directory named something like
MyCustomMetadata.md-meta.xml
- Step 2. Have
**.md
in the forceignore file - Step 3. Deploy to your scratch org, noting that your custom metadata isn’t deployed.
- Step 4. Remove
**.md
in the forceignore file and redeploy to your scratch org. Take note that it deploys the custom metadata.
Expected result
Only .md
extensions should be ignored, not .md-meta.xml
, when adding **.md
to the .forceignore file.
I could understand this behavior if I had added **.md*
to the .forceignore file.
Actual result
.md-meta.xml
files are not deployed with **.md
in the .forceignore file.
Additional information
sfdx-cli/6.56.0 (darwin-x64) node-v8.15.1
@salesforce/plugin-generator 1.0.1 (core) @salesforce/sfdx-trust 2.1.0 (core) builtins 1.0.0 (core) salesforcedx 45.5.0 (core)
Mac OS Mojave 10.14.3 (18D42)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:5
- Comments:18 (3 by maintainers)
Top GitHub Comments
@Kevmo92 , @cnaccio , this looks like a generic issue and not just related to metadata files. I am working on it and will update as soon as I am able to fix it. Thanks!
@Kevmo92 thank you for reporting this. We have added it to our backlog.