Package: gitforge
GIT FORGE API CLIENTSW.I.P.API clients for GitHub & GitLab.INSTALLATIONpip install gitforgeCONFIGURATIONOn first run you will be asked to enter a destination directory to sync to or
check the status of. You will also be asked to enter your Personal Access
Token.Generate aGitHubPersonal Access Tokenhere.Generate aGitLabPersonal Access Tokenhere.These details will be stored in$HOME/.gitforge.cfg. You can edit this file
if you want to change the default destination directory or your access token.The configuration looks something like this:[GitHub]destination=/path/to/directory/to/store/repostoken=GITHUB-PERSONAL-ACCESS-TOKEN[GitLab]destination=/path/to/directory/to/store/repostoken=GITLAB-PERSONAL-ACCESS-TOKENThese defaults can be overridden on the command line with the--tokenand--destinationarguments. See below for more details.COMMANDSsync: Clone repositories(and groups in the case of GitLab)to
destination. If they already exist in destination - update them to the latest
remote commit. This is the default behaviour if no command is specified.status: Check repositories in destination for uncommitted changes.jobs:GitLab ONLYView the log of the last failed CI job run in
repository. This will be opened in a Curses paging window.schedules:GitLab ONLYView all CI pipeline schedules ordered by next run
time.members:GitLab ONLYView all members of groups or projects and their
access level.N.B.If no repositories or groups are specified with-ror-g, then run
command against all of them... This may take a while depending on how many
repositories you have in your account.OPTIONSGITHUBusage: gh [-h] [-d DESTINATION] [-i] [-p {ssh,http}] [-r REPOS [REPOS ...]]
          [-t TOKEN] [-v]
          [{sync,status,jobs,schedules}]

CLI GitHub API Client

positional arguments:
  {sync,status}
                        command to run (default: sync)

optional arguments:
  -d DESTINATION, --destination DESTINATION
                        destination path (default: None)
  -h, --help            show this help message and exit
  -i, --interactive     choose repos interactively (default: False)
  -p {ssh,http}, --protocol {ssh,http}
                        protocol to use (default: ssh)
  -r REPOS [REPOS ...], --repos REPOS [REPOS ...]
                        GitHub repo names (default: None)
  -t TOKEN, --token TOKEN
                        GitHub personal access token (default: None)
  -v, --verbosity       increase verbosity (default: 0)GITLABusage: gl [-h] [-d DESTINATION] [-i] [-p {ssh,http}] [-r REPOS [REPOS ...]]
          [-t TOKEN] [-v] [-g GROUPS [GROUPS ...]]
          [{sync,status,jobs,schedules}]

CLI GitLab API Client

positional arguments:
  {sync,status,jobs,schedules,members}
                        command to run (default: sync)

optional arguments:
  -d DESTINATION, --destination DESTINATION
                        destination path (default: None)
  -g GROUPS [GROUPS ...], --groups GROUPS [GROUPS ...]
                        gitlab group names (default: None)
  -h, --help            show this help message and exit
  -i, --interactive     choose repos interactively (default: False)
  -p {ssh,http}, --protocol {ssh,http}
                        protocol to use (default: ssh)
  -r REPOS [REPOS ...], --repos REPOS [REPOS ...]
                        GitLab repo names (default: None)
  -t TOKEN, --token TOKEN
                        GitLab personal access token (default: None)
  -v, --verbosity       increase verbosity (default: 0)EXAMPLESWith all of these examples if you want more output or a better understanding of
what's going on use the-vargument.Clone or pull all repositories that you are a member of in the directory set
up in your configuration filegitlabfor GitLabgithubfor GitHubN.B.If you have not set up a configuration file or run the command before
you will be prompted for the destination directory and your Personal Access Token.Do the same as above but to an alternative directory, and use HTTP instead of
SSHgitlab -d ~/path/to/alternative/directory -p httpgithub -d ~/path/to/alternative/directory -p httpLimit this action to only the "Example-Groups" and the "Example-Repos"gitlab -d ~/path/to/alternative/directory -g Example-Group-1 Example-Group-2 Example-Repo-1 Example-Repo-2N.B.The group argument only works with GitLab. Also, all child groups will
be included when specifiying a parent group.Choose from a TUI menu the repositories you want to work with from the "Example-Group"gitlab -g example-group -iYou will be presented with a TUI menu which you can use the arrow keys to
navigate and the space bar to select repositories from.View the status of all the repositories in the directory set up in your
configurationgitlab statusfor GitLabgithub statusfor GitHubView job logs of latest failed GitLab CI job from "project-1" & "project-2"
repository in a pagergitlab jobs -r project-1 project-2View CI pipeline schedules of all projects in "group-name" groupgitlab schedules -g group-nameView all members of "group-name" and "project-name"gitlab members -g group-name -r project-name