This action extracts billing and usage numbers from an enterprise and creates a report as a GitHub issue in the repository where it is running.

• enterprise: the slug of the enterprise you wish to query.
• title: the title of the report issue. This title will be used as the issue title and as the top heading of the issue body with the date of the run appended to it. By default the title will have the value GHEC Usage Report.

Environment variables are meant to be used in your workflow file. Take a look at our docs for the proper workflow file syntax.

When dealing with token please take extra care and use the secure store available in every GitHub repo. Once the value has been added to the secure store you can access it in your workflow file by using ${{secrets.SECURE_VALUE}} syntax. Here's a sample workflow file as an example.

A token that has access to the enterprise level data for the enterprise you wish to query. To create a token go to the settings on the account that should manage it.

It's important that this token have the following OAuth scopes:

• admin:enterprise
• admin:org

This token needs to be added to the secrets store of the repository that is using it. Take a look at our docs for more on using secrets with GitHub Actions. Take a look at our docs for more information about personal access tokens and OAuth scopes.

This is the GitHub token that is available in the Action's context. This token will be used to create an issue with the generated report. You don't have to do anything more to use this.

A great way to using this action is with a scheduler. Here's an example workflow file that will run our action on the 28th day of the month, every month:

on:
  schedule:
    - cron: '0 0 28 * *'

jobs:
  report:
    runs-on: ubuntu-latest

    steps:
      - uses: actionsdesk/ghec-enterprise-reporting@v2
        with:
          enterprise: 'awesome-enterprise'
          title: 'Much enterprise reporting'
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          ENTERPRISE_TOKEN: ${{secrets.ENTERPRISE_TOKEN}}

All contributions are welcome, from issues to pull requests. Please take a look at our CONTRIBUTION.md file for details!