-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[tasks] Support VS Code task definitions #247
Comments
I think vs code tasks should be used for that. |
Good idea, VSCode Tasks seem to be already well specified. It looks a bit more complicated to support, but hopefully it will also give us pre-configured Tasks for many existing projects. Do VSCode's and Theia's "Tasks" concepts match 100%? |
Not yet, but they have to eventually (i.e. soon). |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Gitpod is amazing for discovering new projects, and also for reviewing/amending pull requests.
But in both situations, it may happen that you don't know the project's most useful workflows like running tests, linting the code, profiling the app... and you lose a lot of time sifting through various docs (especially if you're new to that project, but also if you haven't worked on it for a while).
Having a few useful project-specific scripts to run directly from the IDE or from the
gp
command-line would be amazing.Project maintainers could configure them in their
.gitpod.yml
, for example:(This could also be useful for projects that have non-standard ways of sending patches, e.g. Firefox with
arc patch
andhg phabsend
; Chromium withgit cl upload
; Linux with sending patches by email...)Terminal
top-menu underRun Task...
(not very discoverable); or directly in a new top-menu just for that project (e.g.Chromium
>git cl upload
).gp
CLI in the terminal.You can find examples of such useful project-specific scripts in Janitor's Dockerfiles repository.
The text was updated successfully, but these errors were encountered: