Skip to content

Commit

Permalink
Update understanding-connections-between-repositories.md | Capitalize…
Browse files Browse the repository at this point in the history
… list lines in understanding-connections-between-repositories. (#35244)

Co-authored-by: Alex Nguyen <[email protected]>
  • Loading branch information
Piyush-r-bhaskar and nguyenalex836 authored Nov 11, 2024
1 parent f06a5af commit a2d226f
Showing 1 changed file with 8 additions and 7 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -44,13 +44,14 @@ The network graph displays the branch history of the entire repository network,

## Listing the forks of a repository

The{% ifversion repositories-forks-page-improvement %} forks page {% else %} Members graph {% endif %} lists the forks of a repository. {% ifversion repositories-forks-page-improvement %}For each fork, you can see:
* how many times the fork has been starred
* the number of direct forks (of the fork)
* the number of open issues
* the number of open pull requests
* when the fork was last updated (that is, the last push to any branch)
* when the fork was created
The {% ifversion repositories-forks-page-improvement %} forks page {% else %} Members graph {% endif %} lists the forks of a repository. {% ifversion repositories-forks-page-improvement %} For each fork, you can see:

Check warning on line 47 in content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md

View workflow job for this annotation

GitHub Actions / lint-content

Liquid `ifversion` (and `elsif`) should not always be true

The Liquid ifversion condition 'repositories-forks-page-improvement' includes all possible versions and will always be true.

Check warning on line 47 in content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md

View workflow job for this annotation

GitHub Actions / lint-content

Liquid `ifversion` (and `elsif`) should not always be true

The Liquid ifversion condition 'repositories-forks-page-improvement' includes all possible versions and will always be true.

* How many times the fork has been starred
* The number of direct forks (of the fork)
* The number of open issues
* The number of open pull requests
* When the fork was last updated (that is, the last push to any branch)
* When the fork was created

You can filter the list of forks to display active, inactive, starred, or archived forks, or to only display forks that have been updated within a specified time period (up to a period of five years). To view the most useful or most active forks, you can sort the list of forks by most starred forks or most recently updated forks, or by the number of open issues or open pull requests.

Expand Down

0 comments on commit a2d226f

Please sign in to comment.