-
Notifications
You must be signed in to change notification settings - Fork 210
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.
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
--readme-path is ignored by the marketplace #1048
Comments
Thanks for reporting this. Could you check both the visual studio code marketplace website and the marketplace inside VSCode and let me know if you see the wrong readme in both cases? |
Hi, both the marketplace website and the Visual Studio Code show the wrong readme. |
What version are you currently using? Could you make sure you are using one of the latest versions, we made a fix in this area not to long ago, this might have fixed your case. |
Hi, I'm not sure about the exact version. The packaging was done by a GitHub runner and |
Great, I'll have a look. In the meantime you can add |
|
There seems to be a bug in vsce. However, the github readme file also seems to be packaged and because it is using the default readme.md filename, it is being shown on the marketplace. The marketplace does not check github repositories for readme files. |
Need to verify with feature owner what the expected behaviour is to understand if this is a marketplace bug or a vsce bug. |
I suggest we reverse our decision to keep the display README.md in its original location and instead just copy its contents over the top level README.md, keeping things simple. |
Hi, I created an extension and when packaging, I specified the path to the readme file
--readme-path README.marketplace.md
. TheREADME.marketplace.md
got included into thevisx
package and the package manifest points to it.Having published the extension, I was surprised that Visual Studio Marketplace ignored the
README.marketplace.md
and shows theREADME.md
from GitHub (!!) as a readme.The text was updated successfully, but these errors were encountered: