Skip to content

docs: add --no-update flag documentation for Git backend#894

Open
santhosh-7777 wants to merge 2 commits intochaoss:mainfrom
santhosh-7777:no-update-git-backend
Open

docs: add --no-update flag documentation for Git backend#894
santhosh-7777 wants to merge 2 commits intochaoss:mainfrom
santhosh-7777:no-update-git-backend

Conversation

@santhosh-7777
Copy link
Copy Markdown

The --no-update flag is already implemented in the Git backend but was not documented in the README.
This PR adds a usage example explaining how to use --no-update for offline usage and reproducibility.
Closes #42

Copy link
Copy Markdown
Member

@sduenas sduenas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I completely forgot about this feature. Thanks!

To approve and merge the PR, I need you to follow the contribution guidelines. In particular, the DCO and the way we write commit messages. Please check of perceval logs about how to do it.

@santhosh-7777 santhosh-7777 force-pushed the no-update-git-backend branch from c007900 to 245218d Compare April 10, 2026 15:06
Signed-off-by: santhosh teja piridi <santhosh.piridi123@gmail.com>
Signed-off-by: santhosh teja piridi <santhosh.piridi123@gmail.com>
@santhosh-7777 santhosh-7777 force-pushed the no-update-git-backend branch from 245218d to 77dba0c Compare April 10, 2026 15:15
@santhosh-7777
Copy link
Copy Markdown
Author

Thanks! I have updated the commit messages as per the guidelines.

@santhosh-7777
Copy link
Copy Markdown
Author

Hi @sduenas , I’ve updated the commit messages and ensured DCO compliance as per the guidelines.
It seems the workflow is awaiting approval — please let me know if anything else is needed from my side. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[git] Option for backends.git.Git allowing for no automatic update of repo

2 participants