Trinity S³AI

Secrets stay out: tick which files git saves

Four files of a small bot project: switch each between saved and ignored and see the alarm when a file with a secret is saved. Only a made-up placeholder is used.

Files of the project

No file leaks: the secret stays on your machine.

No file leaks: the secret stays on your machine.

No file leaks: the secret stays on your machine.

No file leaks: the secret stays on your machine.

Leak: this file holds a secret and git saves it. Anyone who sees the repository sees the secret.

Leak: this file holds a secret and git saves it. Anyone who sees the repository sees the secret.

Leak: this file holds a secret and git saves it. Anyone who sees the repository sees the secret.

Leak: this file holds a secret and git saves it. Anyone who sees the repository sees the secret.

No file leaks: the secret stays on your machine.

No file leaks: the secret stays on your machine.

No file leaks: the secret stays on your machine.

Leak: this file holds a secret and git saves it. Anyone who sees the repository sees the secret.

Leak: this file holds a secret and git saves it. Anyone who sees the repository sees the secret.

Leak: this file holds a secret and git saves it. Anyone who sees the repository sees the secret.

Leak: this file holds a secret and git saves it. Anyone who sees the repository sees the secret.

No file leaks: the secret stays on your machine.

A message to an agent

Read the bot's token from the setting named BOT_TOKEN. The value is in my .env file; do not print it.

Never paste the value itself into a message: a message can be logged, shared or saved.

In .env.example the setting holds only a made-up placeholder:

BOT_TOKEN=your-token-goes-here