Airtable custom extension - should I commit .block/remote.json to github?

PatS 0
Viewed 8

I've created my first AirTable Extension and it's working so I want to commit the code to my github repository. The airtable extension was created using the block init command similar to this:

block init appBlockId --template=https://github.com/Airtable/apps-hello-world myextension

That command creates a sample project which makes it easy to get started. That command created the file .block/remote.json for which I'm asking about.

I don't want to commit anything that contains any private information (that shouldn't be committed to a github repo).

AFAIK, the airtable API key is stored in %USERPROFILE%\AppData\Roaming\.airtableblocksrc.json and not in the current code. See output from block set-api-key keyNotShown command.

block set-api-key keyNotShown
Saving API Key to: C:\Users\user\AppData\Roaming\.airtableblocksrc.json
API Key saved.

The file .block/remote.json which looks like this:

{
    "blockId": "blk0vY. . .",
    "baseId": "appPvD. . ."
}

Searching for a solution

When searching for an answer I see that someone else committed the file, see https://github.com/SiliconValleyInsight/airtable-json-block/blob/master/.block/remote.json so it (hopefully) is something that can and should be committed.

Can I safely commit that file .block/remote.json to github? Does that file contain any private information?

airtable
0 Answers
Related