Skip to content

Conversation

SgtPooki
Copy link
Collaborator

@SgtPooki SgtPooki commented Oct 1, 2025

replacement for #821..

follows much safer two workflow pattern

@SgtPooki SgtPooki marked this pull request as draft October 1, 2025 15:47
@SgtPooki
Copy link
Collaborator Author

SgtPooki commented Oct 1, 2025

FYI I had to kick off the upload workflow manually since it will only run automatically when merged to main.. so i got the build artifact, filecoin-build-pr-822, from https://github.com/filecoin-project/lotus-docs/actions/runs/18170176166?pr=822 and then ran the workflow manually with that input, as well as the build id 18170176166:

image

Workflow: https://github.com/filecoin-project/lotus-docs/actions/runs/18170047009

still debugging some things.. will update this comment when I get it working.

edit:

successful build flow: https://github.com/filecoin-project/lotus-docs/actions/runs/18170176166
successful upload flow: https://github.com/filecoin-project/lotus-docs/actions/runs/18199026793/job/51812897151

@github-actions
Copy link

github-actions bot commented Oct 2, 2025

Filecoin Pin Upload ✅

@SgtPooki SgtPooki marked this pull request as ready for review October 2, 2025 16:22
@SgtPooki
Copy link
Collaborator Author

SgtPooki commented Oct 2, 2025

FYI: Things are working, but this PR should not be merged prior to syncing with @BigLep.. the wallet being used right now is just for calibnet, and we plan on using this to demo some Filecoin Onchain Cloud stuff.

Also, we should probably revert #821

@SgtPooki SgtPooki changed the title fix: safer two workflow filecoin upload [DO NOT MERGE] fix: safer two workflow filecoin upload Oct 2, 2025
@rjan90 rjan90 mentioned this pull request Oct 2, 2025
Copy link
Member

@BigLep BigLep left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The flow is making sense. I'll look again after looking at the action.

if: ${{ github.event.workflow_run.conclusion == 'success' || github.event_name == 'workflow_dispatch' }}
runs-on: ubuntu-latest
env:
GITHUB_TOKEN: ${{ secrets.FILECOIN_PIN_GH_TOKEN }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
GITHUB_TOKEN: ${{ secrets.FILECOIN_PIN_GH_TOKEN }}
GITHUB_TOKEN: ${{ github.token }}

Why do we need a special secret for this?

path: public
minDays: 30
maxTopUp: ${{ github.event_name == 'pull_request' && '0.0001' || '0.01' }}
mode: upload
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume we'll also show how we can store previews with a different dataset.

Comment on lines +17 to +29
- name: Checkout repository
uses: actions/checkout@v4

- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: 20.x

- name: Install dependencies
run: npm ci

- name: Build site
run: npm run build
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was surprised that there wasn't existing CI to hook into, but I guess that is abstracted away by a fleek app or something else

Comment on lines +32 to +34
uses: sgtpooki/filecoin-upload-action@641a2bf866d4ad0c47c98c0ddefaffdd4e628500
with:
path: public
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we also want to be explicit about the mode?

- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: 20.x
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
node-version: 20.x
node-version: 'lts/*'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants