Consider the following approach for adding and deploying new Grafana plugins:
1.) The package is downloaded manually and added locally (to grafana/plugins/...) to a project repository.
2.) Then the repo, updated with the package is pushed to git from where it will be deployed to many production servers.
In this situation, if all the code in /dist/ is in the .gitignore, as it is now, the panel is, of course, not working when the changes are pulled on the servers.
To resolve this, I had to manually modify the .gitignore.
Consider the following approach for adding and deploying new Grafana plugins:
1.) The package is downloaded manually and added locally (to grafana/plugins/...) to a project repository.
2.) Then the repo, updated with the package is pushed to git from where it will be deployed to many production servers.
In this situation, if all the code in /dist/ is in the .gitignore, as it is now, the panel is, of course, not working when the changes are pulled on the servers.
To resolve this, I had to manually modify the .gitignore.