Skip to content

[Feature] Support for launching Codespaces securely #27

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

Open
2 tasks
xames3 opened this issue Nov 30, 2024 · 0 comments
Open
2 tasks

[Feature] Support for launching Codespaces securely #27

xames3 opened this issue Nov 30, 2024 · 0 comments
Assignees
Labels
discussion needed pull requests that need community or team input before moving forwardz documentation updates, additions, or improvements to the project’s documentation enhancement enhancements to existing functionality or the addition of new features high priority pull requests that should be reviewed and merged as a priority due to their importance miscellaneous miscellaneous changes and some of the general inner workings needs testing pull requests that need to be tested or validated before they can be merged work in progress pull requests that are not yet ready for review or merging

Comments

@xames3
Copy link
Owner

xames3 commented Nov 30, 2024

  • like the title says, need to implement a custom directive for providing a button which can launch GitHub Codespaces in a new tab based on the details provided.

  • although the details are not clear yet on how to go about doing this, but the idea here is to have a custom sphinx directive when used

    • will render a button on the UI for launching GitHub Codespaces in a new tab.
    • will have the Codespaces auto configured based on the directive options (iffy about this though).
  • these are some thoughts that do come to mind when having this feature implemented however, things can change and we may need to update our strategy accordingly based on what is and isn't possible without meddling with any credentials.

  • shall put some more details here or below in comments with some relevant links to the documentations.

@xames3 xames3 added discussion needed pull requests that need community or team input before moving forwardz documentation updates, additions, or improvements to the project’s documentation enhancement enhancements to existing functionality or the addition of new features high priority pull requests that should be reviewed and merged as a priority due to their importance miscellaneous miscellaneous changes and some of the general inner workings needs testing pull requests that need to be tested or validated before they can be merged work in progress pull requests that are not yet ready for review or merging labels Nov 30, 2024
@xames3 xames3 self-assigned this Nov 30, 2024
@xames3 xames3 moved this from Todo to Backlog in Open-Source Projects Kanban Board May 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion needed pull requests that need community or team input before moving forwardz documentation updates, additions, or improvements to the project’s documentation enhancement enhancements to existing functionality or the addition of new features high priority pull requests that should be reviewed and merged as a priority due to their importance miscellaneous miscellaneous changes and some of the general inner workings needs testing pull requests that need to be tested or validated before they can be merged work in progress pull requests that are not yet ready for review or merging
Projects
Status: Backlog
Development

No branches or pull requests

1 participant