feat: skip committing unchanged files in 0-cicd-github #1212
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When running 0-cicd-github multiple times, files that haven't changed are also committed. This change adds an option to skip committing unchanged files to prevent unnecessary commits.
antonkovach
changed the title
ludoo
approved these changes
Mar 5, 2023
antonkovach
deleted the
feature/fast-0-cicd-github-skip-commit-unmodified-files
branch
lcaggio
pushed a commit
that referenced
this pull request
May 5, 2023
…1212) When running 0-cicd-github multiple times, files that haven't changed are also committed. This change adds an option to skip committing unchanged files to prevent unnecessary commits. Co-authored-by: Ludovico Magnocavallo <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The cloud-foundation-fabric repository is constantly evolving. Running 0-cicd-github multiple times may be necessary, for instance, when files have changed, and you need to update the repository. However, committing unchanged files can make it challenging to track changes and understand the repository's history. To address this issue, this feature introduces the capability to skip committing unchanged files and improve the repository's readability.
This feature checks whether any changes have been made to the files before committing them. If no changes are detected, the files will not be committed. This results in a cleaner and more focused commit history that is easier to follow and understand.