Skip to content

add no-push option to pretext deploy#952

Merged
oscarlevin merged 2 commits intomainfrom
nopush-deploy
Apr 7, 2025
Merged

add no-push option to pretext deploy#952
oscarlevin merged 2 commits intomainfrom
nopush-deploy

Conversation

@oscarlevin
Copy link
Copy Markdown
Member

This also adds some debug info in case of failures

@oscarlevin oscarlevin merged commit d14618f into main Apr 7, 2025
8 checks passed
@oscarlevin oscarlevin deleted the nopush-deploy branch April 7, 2025 21:07
Comment thread pretext/cli.py
Comment on lines +969 to +973
@click.option(
"--no-push",
is_flag=True,
required=False,
help="Do not push to remote. Useful for CI/CD workflows or in case of authentication errors.",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

It's not clear to me what this does.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Does it only push the gh-pages branch to deploy? (Not the main/active branch?) Or is this supposed to trigger a CI/CD workflow?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

It does not push anything. So the user (or action) needs to run git push origin gh-pages manually.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Action deploys should be using https://github.com/marketplace/actions/deploy-github-pages-site rather than a gh-pages branch, so the CI/CD note here is a little confusing.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Define "should". I would like to allow a workflow where an author could deploy from the command line or an action, which I think needs to use the pretext deploy command. But that doesn't seem to work on an action for authentication reasons. I'm hoping that this would let the action deploy the branch itself

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.

2 participants