Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle config field 'target' when calling publish (arg branch) on GitHub Actions #8

Open
eine opened this issue Sep 5, 2021 · 1 comment

Comments

@eine
Copy link
Collaborator

eine commented Sep 5, 2021

From #7:

the .btd-upstream.yml file looks like this :

# Path to input sources
# Absolute or relative to the location of this configuration file
input: docs

# Path to save intermediate artifacts and products
# Absolute or relative to 'input'
output: _build

# Path to an optional requirements file
# Absolute or relative to 'input'
requirements: requirements.txt

# Domain/repo/branch|tag where sources are located:
source: upstream

# Domain/repo/branch and path where products are to be deployed:
target: gh-pages-upstream

# List of output formats
formats: [ html ]

# List of versions
#versions:
#  - id: master
#    title: ""
#    description: ""
#    warning: ""
#  - id: v0.0.0

# Images to run commands in
images:
  latex: btdi/latex

# Install theme from a repo or a tarball
theme: https://codeload.github.com/buildthedocs/sphinx.theme/tar.gz/v0`

We can see in the list line that he tries to push to gh-pages , but here i choosed gh-pages-upstream as a target in .btd-upstream.yml

@eine
Copy link
Collaborator Author

eine commented Sep 5, 2021

This is partially handled now. FIeld 'target' is passed as-is to the branch argument.

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

No branches or pull requests

1 participant