Skip to content

Commit 01b5881

Browse files
committed
Docs: Remove reference to checking out main branch
We are no longer including information about how to check out github/codeql, so this paragraph doesn't fit any more.
1 parent 0cd6556 commit 01b5881

File tree

1 file changed

+2
-7
lines changed

1 file changed

+2
-7
lines changed

docs/codeql/codeql-cli/upgrading-codeql-databases.rst

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -4,21 +4,16 @@ Upgrading CodeQL databases
44
==========================
55

66
As the CodeQL CLI tools and queries evolve, you may find that some of your
7-
CodeQL databases become out of date. You must upgrade out-of-date databases
7+
CodeQL databases become out of date. You must upgrade out-of-date databases
88
before you can analyze them.
99

1010
Databases become out of date when:
1111

1212
- For databases created using the CodeQL CLI, the version of CLI tools used to
13-
create them is older than your copy of the CodeQL queries.
13+
create them is older than your copy of the CodeQL queries.
1414
- For databases downloaded from LGTM.com, the CodeQL tools used by LGTM.com to create
1515
that revision of the code are older than your copy of the CodeQL queries.
1616

17-
The ``main`` branch of the CodeQL queries is updated more often than both the
18-
CLI and LGTM.com, so databases are most likely to become out of date if you use
19-
the queries on this branch. For more information about the different versions of
20-
the CodeQL queries, see ":ref:`Getting started with the CodeQL CLI <local-copy-codeql-queries>`."
21-
2217
Out-of-date databases must be upgraded before they can be analyzed. This topic
2318
shows you how to upgrade a CodeQL database using the ``database upgrade``
2419
subcommand.

0 commit comments

Comments
 (0)