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

Which version should be published on GitHub pages? #284

Closed
mitar opened this issue Oct 3, 2019 · 4 comments
Closed

Which version should be published on GitHub pages? #284

mitar opened this issue Oct 3, 2019 · 4 comments

Comments

@mitar
Copy link
Member

mitar commented Oct 3, 2019

The package has documentation at:

https://meteor-community-packages.github.io/meteor-roles/

Should we organize it by versions? Where should be the job to build it? GitHub Actions?

@SimonSimCity
Copy link
Member

I just need to run yuidocjs and I get the files generated. For me it's just a question of where should it be pushed. If we just have one version, I'd take the latest version - the one on master.

@mitar
Copy link
Member Author

mitar commented Nov 14, 2019

I would suggest we force push things to gh-pages branch, each version into its own sub-directory. We always clone existing branch, regenerate for a particular version, commit-amend, and force push.

@SimonSimCity
Copy link
Member

Something I just found in a research:

@StorytellerCZ
Copy link
Member

Closing this as we will re-work the docs entirely for all MCP packages to unify things.

@StorytellerCZ StorytellerCZ unpinned this issue Feb 3, 2024
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

No branches or pull requests

3 participants