Skip to content

ci(website): add workflow_dispatch to prod website pipeline - #3657

Closed
aryanmehrotra wants to merge 1 commit into
developmentfrom
feat/website-prod-dispatch
Closed

aryanmehrotra wants to merge 1 commit into
developmentfrom
feat/website-prod-dispatch

Conversation

@aryanmehrotra

Copy link
Copy Markdown
Member

Problem

The production website pipeline (website-prod.yml) only triggers on v*.*.* tag pushes. When the website repo (gofr-dev/website) is updated — new datasource redirect pages, navigation changes, doc fixes — there is no way to redeploy gofr.dev without cutting a new framework release tag.

This became immediately relevant: gofr-dev/website#222 adds the missing go-import redirect pages for cloudsql, influxdb, and kv-store/dynamodb (all tagged in v1.57.0), but the prod website cannot be updated until the next tag push.

Change

Add workflow_dispatch to website-prod.yml so maintainers can trigger a production website rebuild manually from the GitHub Actions UI — no fake patch release required.

How to use

Once gofr-dev/website#222 is merged:

  1. Go to Actions → Build and Deploy → Run workflow
  2. Select development branch, click Run workflow
  3. The pipeline checks out gofr-dev/website:main (with the new pages) and redeploys to prod

Test plan

  • Verify workflow shows "Run workflow" button in Actions UI after merge
  • Trigger manually, confirm prod deploy succeeds
  • Confirm go get gofr.dev/pkg/gofr/datasource/cloudsql@v0.1.0 works after deploy

Allows triggering a production website rebuild without cutting a new
framework release tag — useful when only the website repo changes
(datasource redirect pages, navigation updates, etc.).
@aryanmehrotra
aryanmehrotra deleted the feat/website-prod-dispatch branch June 29, 2026 09:17
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.

1 participant