Linted markdown #3
Conversation
WalkthroughThe Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
| @@ -1,134 +1,163 @@ | |||
| # git-artifact | |||
|
|
|||
| ## The rational for storing artifacts in git | |||
|
|
|||
| I have, over the years in the embbeded enterprise industry, constantly come across many scenarios where zipping, downloading and unzipping generic dependencies and maintaining workspace | |||
There was a problem hiding this comment.
Correct the spelling of "embbeded" to "embedded".
- I have, over the years in the embbeded enterprise industry, constantly come across many scenarios where zipping, downloading and unzipping generic dependencies and maintaining workspace
+ I have, over the years in the embedded enterprise industry, constantly come across many scenarios where zipping, downloading and unzipping generic dependencies and maintaining workspaceCommittable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| I have, over the years in the embbeded enterprise industry, constantly come across many scenarios where zipping, downloading and unzipping generic dependencies and maintaining workspace | |
| I have, over the years in the embedded enterprise industry, constantly come across many scenarios where zipping, downloading and unzipping generic dependencies and maintaining workspace |
README.md
Outdated
| @@ -1,134 +1,163 @@ | |||
| # git-artifact | |||
|
|
|||
| ## The rational for storing artifacts in git | |||
|
|
|||
| I have, over the years in the embbeded enterprise industry, constantly come across many scenarios where zipping, downloading and unzipping generic dependencies and maintaining workspace | |||
| has slowed down turn around time for developers and CI system. Git is a fantastic zipper it self and you get integrity of workspaces for free. | |||
|
|
|||
| Git has always been mentioned to be bad for storing artifacts due to the block chain technology and distrubuted architecture. Git-artifact make sure this problem is handled by storing commits "horisontally" using tags rather than the default "stacked" way. It gives a few advantages compared to standard usage of git: | |||
There was a problem hiding this comment.
Correct "block chain" to "blockchain" and "distrubuted" to "distributed".
- Git has always been mentioned to be bad for storing artifacts due to the block chain technology and distrubuted architecture.
+ Git has always been mentioned to be bad for storing artifacts due to the blockchain technology and distributed architecture.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| Git has always been mentioned to be bad for storing artifacts due to the block chain technology and distrubuted architecture. Git-artifact make sure this problem is handled by storing commits "horisontally" using tags rather than the default "stacked" way. It gives a few advantages compared to standard usage of git: | |
| Git has always been mentioned to be bad for storing artifacts due to the blockchain technology and distributed architecture. Git-artifact make sure this problem is handled by storing commits "horisontally" using tags rather than the default "stacked" way. It gives a few advantages compared to standard usage of git: |
Correct "horisontally" to "horizontally".
- Git-artifact make sure this problem is handled by storing commits "horisontally" using tags rather than the default "stacked" way.
+ Git-artifact make sure this problem is handled by storing commits "horizontally" using tags rather than the default "stacked" way.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| Git has always been mentioned to be bad for storing artifacts due to the block chain technology and distrubuted architecture. Git-artifact make sure this problem is handled by storing commits "horisontally" using tags rather than the default "stacked" way. It gives a few advantages compared to standard usage of git: | |
| Git has always been mentioned to be bad for storing artifacts due to the block chain technology and distrubuted architecture. Git-artifact make sure this problem is handled by storing commits "horizontally" using tags rather than the default "stacked" way. It gives a few advantages compared to standard usage of git: |
| I have, over the years in the embbeded enterprise industry, constantly come across many scenarios where zipping, downloading and unzipping generic dependencies and maintaining workspace | ||
| has slowed down turn around time for developers and CI system. Git is a fantastic zipper it self and you get integrity of workspaces for free. | ||
|
|
||
| Git has always been mentioned to be bad for storing artifacts due to the block chain technology and distrubuted architecture. Git-artifact make sure this problem is handled by storing commits "horisontally" using tags rather than the default "stacked" way. It gives a few advantages compared to standard usage of git: | ||
|
|
||
| - Firstly; You can garbage collect intermidiate artifacts by just deleting the tag |
There was a problem hiding this comment.
Correct "intermidiate" to "intermediate".
- Firstly; You can garbage collect intermidiate artifacts by just deleting the tag
+ Firstly; You can garbage collect intermediate artifacts by just deleting the tagCommittable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| - Firstly; You can garbage collect intermidiate artifacts by just deleting the tag | |
| Firstly; You can garbage collect intermediate artifacts by just deleting the tag |
| Triggering of new builds or tests are done the normal way as known from triggering your pipelines of source code - push or pull - simple.. | ||
|
|
||
| ### Save money | ||
|
|
||
| You can save additional license and maintainance cost and/or coqnative load by maintaining and using an additional system for artifacts. You can handle it with your current git repository manager. |
There was a problem hiding this comment.
Correct "maintainance" to "maintenance" and "coqnative" to "cognitive".
- You can save additional license and maintainance cost and/or coqnative load by maintaining and using an additional system for artifacts.
+ You can save additional license and maintenance cost and/or cognitive load by maintaining and using an additional system for artifacts.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| You can save additional license and maintainance cost and/or coqnative load by maintaining and using an additional system for artifacts. You can handle it with your current git repository manager. | |
| You can save additional license and maintenance cost and/or cognitive load by maintaining and using an additional system for artifacts. You can handle it with your current git repository manager. |
| A few remarks, aspects and thoughts when storing the artifacts | ||
|
|
||
| A few remarks, aspects and thoughts when storing the artifacts | ||
|
|
||
| - easy to append artifacts as stages evolves with more artifacts |
There was a problem hiding this comment.
Start the sentence with an uppercase letter.
- easy to append artifacts as stages evolves with more artifacts
+ Easy to append artifacts as stages evolves with more artifactsCommittable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| - easy to append artifacts as stages evolves with more artifacts | |
| Easy to append artifacts as stages evolves with more artifacts |
| A few remarks, aspects and thoughts when storing the artifacts | ||
|
|
||
| A few remarks, aspects and thoughts when storing the artifacts | ||
|
|
||
| - easy to append artifacts as stages evolves with more artifacts | ||
| - no need to zip before upload - just commit as the artifact should be used. | ||
| - easy to add information, environment, tools and git source sha1 in the artifact for traceability and later reproduction |
There was a problem hiding this comment.
Start the sentence with an uppercase letter.
- easy to add information, environment, tools and git source sha1 in the artifact for traceability and later reproduction
+ Easy to add information, environment, tools and git source sha1 in the artifact for traceability and later reproductionCommittable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| - easy to add information, environment, tools and git source sha1 in the artifact for traceability and later reproduction | |
| Easy to add information, environment, tools and git source sha1 in the artifact for traceability and later reproduction |
README.md
Outdated
| [0.2/test] | ||
| | | ||
| [0.1/bin] [0.2/bin] [0.3/bin] | ||
| | / / | ||
| <main> | ||
| ``` | ||
|
|
||
| `git-artifacts` has all the functions available that make the above history straight for and natural workflow. |
There was a problem hiding this comment.
Start the sentence with an uppercase letter.
- `git-artifacts` has all the functions available that make the above history straight for and natural workflow.
+ `Git-artifacts` has all the functions available that make the above history straight for and natural workflow.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| `git-artifacts` has all the functions available that make the above history straight for and natural workflow. | |
| `Git-artifacts` has all the functions available that make the above history straight for and natural workflow. |
| cd my-git-artifact-path | ||
| cp -rf <build-dir>/my.lib /include . | ||
| git artifact add-n-push -t v1.0 | ||
| ``` | ||
|
|
||
| The artifact v1.0 is now commited, pushed _and_ importantly - the workspace is set back to the default branch of the remote repository. It is now ready to make a new artifact based on the default branched |
There was a problem hiding this comment.
Correct "commited" to "committed".
- The artifact v1.0 is now commited, pushed _and_ importantly - the workspace is set back to the default branch of the remote repository.
+ The artifact v1.0 is now committed, pushed _and_ importantly - the workspace is set back to the default branch of the remote repository.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| The artifact v1.0 is now commited, pushed _and_ importantly - the workspace is set back to the default branch of the remote repository. It is now ready to make a new artifact based on the default branched | |
| The artifact v1.0 is now committed, pushed _and_ importantly - the workspace is set back to the default branch of the remote repository. It is now ready to make a new artifact based on the default branched |
| `git artifact` work great out of the box without any extensions like LFS. It can though still be interesting to commit an `git-lfs` configuration to the default branch. | ||
| - Artifact sets that can many common binary/large files from version to version will then be able to detect that it already have have this file in the LFS storage and do not have to fetch/push it again. | ||
|
|
||
| `git artifact` work great out of the box without any extensions like LFS. It can though still be interesting to commit an `git-lfs` configuration to the default branch |
There was a problem hiding this comment.
Start the sentence with an uppercase letter.
- `git artifact` work great out of the box without any extensions like LFS.
+ `Git artifact` works great out of the box without any extensions like LFS.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| `git artifact` work great out of the box without any extensions like LFS. It can though still be interesting to commit an `git-lfs` configuration to the default branch | |
| `Git artifact` works great out of the box without any extensions like LFS. It can though still be interesting to commit an `git-lfs` configuration to the default branch |
There was a problem hiding this comment.
Actionable comments posted: 13
Review Details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- README.md (2 hunks)
Additional Context Used
LanguageTool (24)
README.md (24)
Near line 3: Did you mean “rationale” (=an explanation / underlying reason)?
Context: # git-artifact ## The rational for storing artifacts in git I have, o...
Near line 6: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ystem. Git is a fantastic zipper it self and you get integrity of workspaces for fre...
Near line 8: This word is normally spelled as one.
Context: ...be bad for storing artifacts due to the block chain technology and distrubuted architecture...
Near line 14: Two consecutive dots
Context: ...s of source code - push or pull - simple.. ### Save money You can save additiona...
Near line 27: It seems that “to” is missing before the verb.
Context: ...y to the artifact. It will then be easy restore the source for diff and debugging ### ...
Near line 33: The verb form ‘do’ does not appear to fit in this context.
Context: ...ts when retrieving the artifacts - The consumer do not need anything than standard git - P...
Near line 35: Two consecutive dots
Context: ...for submodule usage btw ), repo tool or .. - Even a consumer can be a producer by ...
Near line 41: The word “hence” is an adverb that can’t be used like a conjunction, and therefore needs to be separated from the sentence.
Context: ...How is it done Git normally stacks the history hence you cannot delete commit in the middle ...
Near line 41: The abbreviation “i.e.” (= that is) requires two periods.
Context: ...artifact` make a "horizontal" history - i.e the commits are not stacked on top of e...
Near line 81: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...acts. It can also run in branch mode. It can maintain alatestbranch which n...
Near line 85: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...s in the PATH, thengitcan use it as an command likegit artifact. It is now ...
Near line 89: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...t artifact` also have command to do that and it states that this repository is "spec...
Near line 101: It seems that the adverb “not” is incorrect in this context.
Context: ...ure the "constumer" desire it. There is not reason to tar or zip it. Git will handling thi...
Near line 101: Modal verbs like ‘can’ or ‘will’ require the following verb to be in its base form.
Context: ...s not reason to tar or zip it. Git will handling this for optimized storage and easiness...
Near line 134: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ... advantage. Let say you create a library and you run a lot of tests in a later stage...
Near line 134: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ...et say you create a library and you run a lot of tests in a later stage and the result i...
Near line 139: Consider adding two commas here.
Context: ...a new artifact ( see above ) You should of course consider this in your naming convension...
Near line 150: The word “checkout” is a noun. The verb is spelled with a white space.
Context: ... it gives the developers easy access to checkout the correct version that was used to bu...
Near line 152: This word is normally spelled as one.
Context: ...y it actually possible to create a full block-chain of everything that was involved in prod...
Near line 160: Two consecutive dots
Context: ...cleaning artifacts TODO: based on count.. ## Advanced ### LFSgit artifactw...
Near line 168: The verb form ‘have’ does not seem to be suitable in this context.
Context: ... be able to detect that it already have have this file in the LFS storage and do not...
Near line 169: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...u can download all tags without checkout and then you can search for meta-data in th...
Near line 169: Consider a shorter alternative to avoid wordiness.
Context: ...ffering large data transfer and storage in order to clean. ### Promotions There are genra...
Near line 184: There may an error in the verb form ‘be append’.
Context: ...either be a new unrelated tag or it can be append on top if a release candidate tag.
| @@ -1,38 +1,46 @@ | |||
| # git-artifact | |||
|
|
|||
| ## The rational for storing artifacts in git | |||
|
|
|||
There was a problem hiding this comment.
Correct the term "rational" to "rationale".
- ## The rational for storing artifacts in git
+ ## The rationale for storing artifacts in gitCommittable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| ## The rationale for storing artifacts in git |
| @@ -1,38 +1,46 @@ | |||
| # git-artifact | |||
|
|
|||
| ## The rational for storing artifacts in git | |||
|
|
|||
| I have, over the years in the embbeded enterprise industry, constantly come across many scenarios where zipping, downloading and unzipping generic dependencies and maintaining workspace | |||
| has slowed down turn around time for developers and CI system. Git is a fantastic zipper it self and you get integrity of workspaces for free. | |||
There was a problem hiding this comment.
Add a comma before "and" to connect two independent clauses.
- Git is a fantastic zipper it self and you get integrity of workspaces for free.
+ Git is a fantastic zipper itself, and you get integrity of workspaces for free.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| has slowed down turn around time for developers and CI system. Git is a fantastic zipper it self and you get integrity of workspaces for free. | |
| has slowed down turn around time for developers and CI system. Git is a fantastic zipper itself, and you get integrity of workspaces for free. |
| I have, over the years in the embbeded enterprise industry, constantly come across many scenarios where zipping, downloading and unzipping generic dependencies and maintaining workspace | ||
| has slowed down turn around time for developers and CI system. Git is a fantastic zipper it self and you get integrity of workspaces for free. | ||
|
|
||
| Git has always been mentioned to be bad for storing artifacts due to the block chain technology and distrubuted architecture. `git-artifact` make sure this problem is handled by storing commits "horisontally" using tags rather than the default "stacked" way. It gives a few advantages compared to standard usage of git: | ||
| Git has always been mentioned to be bad for storing artifacts due to the block chain technology and distrubuted architecture. `git-artifact` makes sure this problem is handled by storing commits "horisontally" using tags rather than the default "stacked" way. It gives a few advantages compared to standard usage of git: |
There was a problem hiding this comment.
Correct the spelling of "block chain" to "blockchain" and "distrubuted" to "distributed".
- Git has always been mentioned to be bad for storing artifacts due to the block chain technology and distrubuted architecture.
+ Git has always been mentioned to be bad for storing artifacts due to the blockchain technology and distributed architecture.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
Git has always been mentioned to be bad for storing artifacts due to the blockchain technology and distributed architecture. `git-artifact` makes sure this problem is handled by storing commits "horisontally" using tags rather than the default "stacked" way. It gives a few advantages compared to standard usage of git:
| - Firstly; You can garbage collect intermidiate artifacts by just deleting the tag | ||
| - Secondly; You only fetch what you need - even without using shallow. | ||
|
|
||
| ### CI/CD integration | ||
|
|
||
| Triggering of new builds or tests are done the normal way as known from triggering your pipelines of source code - push or pull - simple.. |
There was a problem hiding this comment.
Remove the extra period.
- Triggering of new builds or tests are done the normal way as known from triggering your pipelines of source code - push or pull - simple..
+ Triggering of new builds or tests are done the normal way as known from triggering your pipelines of source code - push or pull - simple.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| Triggering of new builds or tests are done the normal way as known from triggering your pipelines of source code - push or pull - simple.. | |
| Triggering of new builds or tests are done the normal way as known from triggering your pipelines of source code - push or pull - simple. |
| A few remarks, aspects and thoughts when storing the artifacts | ||
|
|
||
| A few remarks, aspects and thoughts when storing the artifacts | ||
|
|
||
| - easy to append artifacts as stages evolves with more artifacts | ||
| - no need to zip before upload - just commit as the artifact should be used. | ||
| - easy to add information, environment, tools and git source sha1 in the artifact for traceability and later reproduction | ||
| - add the source code as a dependency to the artifact. It will then be easy restore the source for diff and debugging |
There was a problem hiding this comment.
Add "to" before "restore".
- It will then be easy restore the source for diff and debugging
+ It will then be easy to restore the source for diff and debuggingCommittable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
- add the source code as a dependency to the artifact. It will then be easy to restore the source for diff and debugging
| The tool uses tags hence the producer need to tag push-rights. It is also beneficial to have tag delete-rights to clean old artifacts. | ||
|
|
||
| It can also run in branch mode. It can maintain a `latest` branch which needs to be force pushed or delete + push rights. The concept is similar to docker concept of `<image>/latest`. It is only important if you want to use tracking branches without using `git-artifact`. It could be in context of `submodules` or `repo manifests`. | ||
|
|
||
| ### Installation | ||
|
|
||
| Download or clone this repo (`git-artifact`) and add make it available in the PATH. Given that `git-artifact` is in the PATH, then `git` can use it as an command like `git artifact`. It is now integrated with git and git is extended. |
There was a problem hiding this comment.
Use "a" instead of "an" before "command".
- Given that `git-artifact` is in the PATH, then `git` can use it as an command like `git artifact`.
+ Given that `git-artifact` is in the PATH, then `git` can use it as a command like `git artifact`.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| Download or clone this repo (`git-artifact`) and add make it available in the PATH. Given that `git-artifact` is in the PATH, then `git` can use it as an command like `git artifact`. It is now integrated with git and git is extended. | |
| Download or clone this repo (`git-artifact`) and add make it available in the PATH. Given that `git-artifact` is in the PATH, then `git` can use it as a command like `git artifact`. It is now integrated with git and git is extended. |
| git artifact init --url=<remote_url> --path my-git-artifact-path | ||
| ``` | ||
|
|
||
| ### Add the artifact | ||
|
|
||
| The repository and path initialize above ready to use. Copy the artifacts to your path in the folder structure the "constumer" desire it. There is not reason to tar or zip it. Git will handling this for optimized storage and easiness. |
There was a problem hiding this comment.
Correct grammatical errors.
- The repository and path initialize above ready to use. Copy the artifacts to your path in the folder structure the "constumer" desire it. There is not reason to tar or zip it. Git will handling this for optimized storage and easiness.
+ The repository and path initialized above are ready to use. Copy the artifacts to your path in the folder structure the "consumer" desires it. There is no reason to tar or zip it. Git will handle this for optimized storage and easiness.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| The repository and path initialize above ready to use. Copy the artifacts to your path in the folder structure the "constumer" desire it. There is not reason to tar or zip it. Git will handling this for optimized storage and easiness. | |
| The repository and path initialized above are ready to use. Copy the artifacts to your path in the folder structure the "consumer" desires it. There is no reason to tar or zip it. Git will handle this for optimized storage and easiness. |
| vX.Y.Z/release-note | ||
| vX.Y.Z/test | ||
| vX.Y.Z/src | ||
| vX.Y.Z/lib | ||
| ``` | ||
|
|
||
| ### Add the source code that was used to build the artifact | ||
|
|
||
| The source code in many companies and open-source projects are free to view, debug and edit. You can make it easy accessable by adding the source code as submodule and sha1 in to the artifact history. It sounds odd, but it gives the developers easy access to checkout the correct version that was used to build artifact. |
There was a problem hiding this comment.
Correct "checkout" to "check out".
- It sounds odd, but it gives the developers easy access to checkout the correct version that was used to build artifact.
+ It sounds odd, but it gives the developers easy access to check out the correct version that was used to build the artifact.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| The source code in many companies and open-source projects are free to view, debug and edit. You can make it easy accessable by adding the source code as submodule and sha1 in to the artifact history. It sounds odd, but it gives the developers easy access to checkout the correct version that was used to build artifact. | |
| The source code in many companies and open-source projects are free to view, debug and edit. You can make it easy accessable by adding the source code as submodule and sha1 in to the artifact history. It sounds odd, but it gives the developers easy access to check out the correct version that was used to build the artifact. |
|
|
||
| `git artifact` work great out of the box without any extensions like LFS. It can though still be interesting to commit an `git-lfs` configuration to the default branch | ||
|
|
||
| - Artifact sets that can many common binary/large files from version to version will then be able to detect that it already have have this file in the LFS storage and do not have to fetch/push it again. |
There was a problem hiding this comment.
Correct the repeated word "have".
- Artifact sets that can many common binary/large files from version to version will then be able to detect that it already have have this file in the LFS storage and do not have to fetch/push it again.
+ Artifact sets that can handle many common binary/large files from version to version will then be able to detect that it already has this file in the LFS storage and does not have to fetch/push it again.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| - Artifact sets that can many common binary/large files from version to version will then be able to detect that it already have have this file in the LFS storage and do not have to fetch/push it again. | |
| Artifact sets that can handle many common binary/large files from version to version will then be able to detect that it already has this file in the LFS storage and does not have to fetch/push it again. |
|
|
||
| This way requires you to create a tag using a release tag pattern. The tag can either be a new unrelated tag or it can be append on top if a release candidate tag. |
There was a problem hiding this comment.
Correct the verb form "be append" to "be appended".
- The tag can either be a new unrelated tag or it can be append on top if a release candidate tag.
+ The tag can either be a new unrelated tag or it can be appended on top of a release candidate tag.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| This way requires you to create a tag using a release tag pattern. The tag can either be a new unrelated tag or it can be append on top if a release candidate tag. | |
| This way requires you to create a tag using a release tag pattern. The tag can either be a new unrelated tag or it can be appended on top of a release candidate tag. |
Fixed markdown linter errors in README.md
Summary by CodeRabbit
New Features
Documentation
git-artifacttool.