Package: github-commit-status
A simple command line for updating a commit’s status in GitHubProject and Build StatusGitHub repoOnline DocumentationFree SoftwareHow to UseBackground and PurposeIn GitHub, Pull Requests can have some checks against the code in question.
This is a great way to check for things such as white space, coding standards,
etc. Continuous Integration tools, like Travis, use this to update the status
of the commit that you see in Pull Requests in GitHub.This is a fairly simple integration and you can also place your own checks here.
In the following example, I made the status pending with a yellow circle with
the phrase “You know you can change this, right?”This command line tool will allow you to update the status of any commit that
you have access to in GitHub. It was built to be a teaching tool for a course
on Source Control Management (Git) and GitHub integrations. However, it is
stable and can be used in production seamlessly – especially environments
where it makes sense to use a command line instead of your own library.Gather the info that you needTo update the status of a commit in a Pull Request, you will need to provide
some basic information:The name of the GitHub repository which has your Pull RequestThe commit SHA that is to be updated (e.g., the last commit  in a pull
request)The desired status of the commit:“success” (GitHub displays a green checkmark)“pending” (GitHub displays a yellow circle)“error” or “failure” (GitHub displays a red ‘X’)Description (e.g., “You know you can change this, right?” was the description
used in the example above)Authorization token. This will allow the command to act like you.
Instructions on how to create this token follow.Personal Access TokenThis tool is intended to change the status of a GitHub Pull Request. That is
something that should only be allowed by someone who is authorized. You
wouldn’t want someone that you hadn’t authorized updating your Pull Request
statuses.You will need to generate a Personal Access Token so that this command line can
act like you. Keep this token safe – it is like a password.This is done in your account settings configuration. Don’t confuse the
project’s settings with your settings for your account.Profile SettingsIn the upper right hand corner, you will see your avatar photo (or a default
avatar image). When you click the avatar, there will be a drop down menu with
menu options. Choose theSettingsoption.Developer SettingsOn the next page that is loaded, the Profile settings page, you will see another
menu to the left. It is a longer menu where the bottom looks similar to the
following. ChooseDeveloper settings:Create a Personal Access TokenOn the next page, the Developer Settings page, you will see one final menu.
ChoosePersonal access tokens:Press the button toGenerate new token.In theToken descriptionenter “github_commit_status”. This way we
remember the purpose of this token.Select therepo:statusscope checkbox. Anyone who has this token could
update your GitHub account. So, keep the scope of this token so that it canonlyupdate or access the commit status.Scroll to the bottom of click the greenGenerate tokenbutton.Your token should now be displayed. This token will only display this time.
You won’t be able to see it again and it cannot be recovered.Keep your token safe so that you can use it with this program. Remember, if
someone else can access this token, they can update your GitHub statuses -
even if you don’t want them to.Example: Prompt modeIf you only need to use this command line rarely, there’s no need to worry about
getting the command line arguments correct - you will be prompted for any
required arguments that are missing. This is ideal for students in my class who
only need to update a Pull Requests a few times for a homework assignment. See
the next section for a more scriptable mode and example.Install:pip install github_commit_statusRun:github_commit_status promptEnter the data that you have collected (e.g., Personal Access Token, commit
SHA, etc.)Here is an example that I used for one of my projects. Remember, don’t let
your Personal Access Token get published like I intentionally did here. I
ensured this token was deleted before I published this:$ github_commit_status prompt

GitHub Token [26fee6a5d440111a2648312d458b6b4e44c20c1d]:
Name of the GitHub repository []: my_target_repo
Commit SHA []: 2dd5f9ce1108d69e863444ee6486e64e0299868f
Status: pending
Description: Tests have started

GitHub has been updated.Example: For scriptingThis command can also be used for shell scripts that need to update GitHub.For security reasons, this mode/subcommand does not provide an option for:--github-tokenas this is preserved in most shell histories. Instead, the
environment variableGITHUB_COMMIT_STATUS_TOKENshould already be set. For
example, in a bash shell:export GITHUB_COMMIT_STATUS_TOKEN=26fee6a5d440111a2648312d458b6...Install:pip install github_commit_statusTo see command line options that can be provided:$ github_commit_status update --help
Usage: github_commit_status update [OPTIONS]

  If all options are provided, update GitHub

Options:
  --repo TEXT                     Name of the GitHub repository  [required]
  --commit TEXT                   The 40 character SHA1 string for the commit.
                                  [required]
  --status [error|failure|pending|success]
                                  The status of the commit  [required]
  --description TEXT              Description for the test  [required]
  --help                          Show this message and exit.Here is an example usage. Remember, your Personal Access Token
needs to be pre-set in environment variableGITHUB_COMMIT_STATUS_TOKEN:$ github_commit_status update --repo=my_target_repo \
    --commit="2dd5f9ce1108d69e863444ee6486e64e0299868f" \
    --status=pending \
    --description="Tests are running."Make this better by ContributingThis is an Open Source project and contributions are always welcome, and they
are greatly appreciated! Every little bit helps, and credit will always be
given.You can contribute in many ways:Report bugsWrite DocumentationFix bugsTo maximize the chance that your hard work gets merged, we have these guidelines
to guide you along the way to a successfully merged Pull Request:Contributing