actions / actions/deploy-pages
Feature Request: two phase run
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 953
- Forks
- 143
- Avg merge
- 35m
- Merged PRs (30d)
- 1
Description
I have a Hugo site and Hugo has a characteristic where it needs to know the base url at build time to generate absolute links properly.
The problem is that it creates a egg and chicken problem where I need the base url to build the site but I need the artifact to know for sure what could be the base url.
Right now I am not doing preview deployments so it's not a huge deal as I can just hardcode the hostname, but it will if someone wants to do preview deploys.
Basically what I suggest is that the workflow creates the slot at first, gives the base URL and confirms the deploy as a finish step, like those cleanup tasks some workflows have.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named in the issue. Start by tracing the action's deployment flow and how it receives the generated base URL. Done means the workflow can create the deployment slot, expose its base URL for the build, and confirm the deployment as a final step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, hugo, javascript
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100