From 2ee0a62db077c6e96ae2002a6f9fc1196146710a Mon Sep 17 00:00:00 2001 From: Mike Frysinger Date: Tue, 4 May 2021 15:16:38 -0400 Subject: [PATCH] release-process: document the rate limiting in automatic updates We check for updates only once per day, so clarify the docs. Change-Id: Ib669ca6ebc67bc13204996fa40e1a3a82012295e Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/305145 Reviewed-by: Raman Tenneti Tested-by: Mike Frysinger --- docs/release-process.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/release-process.md b/docs/release-process.md index 43209eb0..3373aae6 100644 --- a/docs/release-process.md +++ b/docs/release-process.md @@ -83,7 +83,8 @@ control how repo finds updates: * `--repo-rev`: This tells repo which branch to use for the full project. It defaults to the `stable` branch (`REPO_REV` in the launcher script). -Whenever `repo sync` is run, repo will check to see if an update is available. +Whenever `repo sync` is run, repo will, once every 24 hours, see if an update +is available. It fetches the latest repo-rev from the repo-url. Then it verifies that the latest commit in the branch has a valid signed tag using `git tag -v` (which uses gpg). @@ -95,6 +96,11 @@ If that tag is valid, then repo will warn and use that commit instead. If that tag cannot be verified, it gives up and forces the user to resolve. +### Force an update + +The `repo selfupdate` command can be used to force an immediate update. +It is not subject to the 24 hour limitation. + ## Branch management All development happens on the `main` branch and should generally be stable.