If you do this, your tags will not be updated - but I don't think is a concern here. The table below maps some of the key previous chart versions and GitLab versions. Download latest CFLint standalone JAR ( CFLint-1.2.0. Specifically, you need to omit -tags to skip this step of the process. Linter installation Download and install latest Java SE 8+ JRE, or JDK if you plan to build it yourself. There isn't anything wrong with having a "moving" tag like latest, that just isn't something VSCode takes into account (personal opinion).Īlternatively, you can avoid the issue by using the command line and manually entering the git pull command. VSCode will pull all tags by default, thus you get the error. If you apply the change from the remote you will overwrite your local tag. Example: git checkout -b HEAD is now at feb2b2944 Committing updated structure rtd-command-info start-time: T17:59:30.132921Z, end-time: T17:59:30.238881Z, duration: 0, exit-code: 0 git clean -d -f -f rtd-command-info start-time: T17:59:30.642119Z, end-time: T17:59:30.825552Z, duration: 0, exit-code. So, the "error" is that you have in your local a tag called latest pointing to commit X - but the remote has a tag called latest pointing to commit Y. The main difference is that git (as far as I know) assumes tags will not change, where branches are expected to be updated. Tags are just references to specific commits (just like branch names). Or add this "git.pullTags": false in the settings.json file` Since you say it's unclear what's going wrong, I assume you're not using that tag for anything and you just want to do your own work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |