Skip to content

GitHub Stars and Lists

Start with a connected interface. Choose Web for your own setup, or CLI / Agent for terminal instructions.

Set up in the Web app

  1. Create a personal access token for the account whose Stars and Lists you want to collect, using GitHub's token instructions. Its account and permissions determine what the collector can see.
  2. Prepare the Extension: inkcre/github version 0.3.0 on Core Host 0.2.x. Select the online Core client to install and enable the collector.
  3. Open Sources and the create-source form. Enter Nickname My GitHub saves and choose Type extensions.github.stars.Source.
  4. Enter this object in Config, replace the token, and save/create:
json
{ "github_token": "YOUR-GITHUB-TOKEN" }
  1. Open the saved Source and collect once. Index and search for a repository you starred before adding a schedule.

Keep your token and configuration private. Each run synchronizes current Stars and Lists; this is not a code backup or a full GitHub activity archive.

Start with a working instance and a connected CLI. The version below targets Core Host 0.2.x; check the linked release listing for other Host versions. If already installed, inspect inkcre-cli extension get inkcre/github before changing it. Keep credential files and command output private.

  1. Create a personal access token for the account whose Stars and Lists you want to collect, following GitHub's token instructions. Its account and permissions determine which data is visible.

  2. Enable the Extension:

    sh
    inkcre-cli extension install inkcre/github --version 0.3.0
    inkcre-cli extension enable inkcre/github
  3. Save github.json with your token:

    json
    {
      "nickname": "My GitHub saves",
      "config": { "github_token": "YOUR-GITHUB-TOKEN" }
    }
    sh
    inkcre-cli source create --type extensions.github.stars.Source --input github.json
  4. Collect the returned Source ID using Run a Collection. After indexing, search for a repository you starred. Each run synchronizes current Stars and Lists; it is not a code backup or a full GitHub activity archive.

See the GitHub collector and published releases.

Next: index and search for a known item, then schedule collection.