You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello maintainers.
I would like to add gitpod to your repo to help beginners contribute.
Gitpod is an online IDE which can be launched from any GitHub page. Within seconds, Gitpod provides a fully working development environment, including a VS Code-powered IDE and a cloud-based Linux container explicitly configured for the project
I have seen one of your repo adopt gitpod to help new contributors in their open-source journey. It's hassle-free. You don't need to worry about dependencies not being present, since gitpod does all the heavy lifting.
I can add a badge to your repo in the CONTRIBUTING.md file similar to this one:
🎤 Pitch
Gitpod is highly contextual, such that it opens the IDE in the correct mode depending on the context:
If you are looking at a particular file of a certain commit on GitHub, starting a Gitpod workspace will check out the right version and open the file you’ve been looking at in the IDE.
Starting a Gitpod workspace from an issue will automatically create a branch and preconfigure the commit message.
Once you are in the IDE, you can interact with GitHub in various ways. Besides the obvious Git integration, you can do things like commenting inline in editors, approving and even merging PRs.
👀 Have you spent some time to check if this issue has been raised before?
🔖 Feature description
Hello maintainers.
I would like to add gitpod to your repo to help beginners contribute.
I can add a badge to your repo in the CONTRIBUTING.md file similar to this one:
🎤 Pitch
If you are looking at a particular file of a certain commit on GitHub, starting a Gitpod workspace will check out the right version and open the file you’ve been looking at in the IDE.
Starting a Gitpod workspace from an issue will automatically create a branch and preconfigure the commit message.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: