Remove from GitHub #1

New issue

Open

opened 2026-01-26 00:33:41 +01:00 by geoffrey · 0 comments

geoffrey commented

2026-01-26 00:33:41 +01:00

Owner

This things relies on Figma but removing it from GitHub would be nice... Though I tried and the dependency on GitHub actions is strong.

This is what I did:

Set secrets. FIGMA_FILE_KEY is bbaYMGaR5jRuXt1UjfBZwp, it's not really a secret. FIGMA_ACCESS_TOKEN can be generated from the Figma settings, they last at most 90 days so no point in finding an old one.
See diff in attached file that I can't name .diff because Forgejo says no.

Even with that, the export could run but fail at the post steps, because trying to cache pnpm which does not exist? Do the actions have stable ordering when it comes to post steps? Good question.
It also did not complain at the "make a commit" step, but it had no change to do so maybe it did not even try.

This things relies on Figma but removing it from GitHub would be nice... Though I tried and the dependency on GitHub actions is strong. This is what I did: - Set secrets. `FIGMA_FILE_KEY` is `bbaYMGaR5jRuXt1UjfBZwp`, it's not really a secret. `FIGMA_ACCESS_TOKEN` can be generated from the Figma settings, they last at most 90 days so no point in finding an old one. - See diff in attached file that I can't name `.diff` because Forgejo says no. Even with that, the export could run but fail at the post steps, because trying to cache `pnpm` which does not exist? Do the actions have stable ordering when it comes to post steps? Good question. It also did not complain at the "make a commit" step, but it had no change to do so maybe it did not even try.

fringer-forgejo.txt

2.5 KiB

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

geoffrey/fringer-cursors#1

No description provided.

Rows
Columns