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

Create docs page for gh-scoped-creds #65

Closed
jmunroe opened this issue Jan 29, 2024 · 4 comments
Closed

Create docs page for gh-scoped-creds #65

jmunroe opened this issue Jan 29, 2024 · 4 comments
Assignees

Comments

@jmunroe
Copy link
Collaborator

jmunroe commented Jan 29, 2024

Motivated by the request in leap-stc/leap-stc.github.io#129 , let's create a single markdown which covers the content covered in https://blog.jupyter.org/securely-pushing-to-github-from-a-jupyterhub-3ee42dfdc54f

While documenting gh-scoped-creds is generally useful, I think this could be nice specific example of creating a piece of content that could be included in a JupyterBook that 2i2c maintains (community showcase handbook) AND reused downstream by a community partner.

@jnywong
Copy link
Member

jnywong commented Feb 9, 2024

Documentation deployed to https://2i2c.org/community-showcase/user/topics/data/git.html

@jnywong
Copy link
Member

jnywong commented Feb 9, 2024

Currently, the community showcase handbook is a WIP and not publicised. If this piece of documentation is approved for use, then should it be upstreamed to the Service Guide at docs.2i2c.org? Or will this continue to serve as a standalone document for communities to adopt downstream?

@jnywong
Copy link
Member

jnywong commented Feb 9, 2024

A link to the single markdown file as requested in the original comment can be found here: https://github.com/2i2c-org/community-showcase/blob/main/handbook/user/topics/data/git.md

@jnywong
Copy link
Member

jnywong commented Feb 9, 2024

Closing this issue as done and I will turn the question above about how this piece of documentation may be adopted upstream/downstream into a separate issue.

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

2 participants