sapling/ci
Shish 1a0d7106a4 Add a devcontainer config (#807)
Summary:
Add a devcontainer config

My laptop is full of weird versions of weird tools. Sapling requires specific versions of specific tools. It's nice to be able to open the sapling folder in vscode and get a prompt for "would you like to do your development inside a container with all the correct tools pre-installed?" :) This also allows people on github to click a button to open in github's web-based container-IDE and start developing without installing anything at all, though I don't know if we'd expect anybody to do that

For starters I'm using the CI build image without changes to try and keep the maintenance burden as small as possible, though it would be possible to use a separate layer within the Dockerfile (eg if we wanted to install extra tools that are useful for dev but not needed for building), or have a totally separate Dockerfile

 ---
[//]: # (BEGIN SAPLING FOOTER)
Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/facebook/sapling/pull/807).
* __->__ https://github.com/facebook/sapling/issues/807
* https://github.com/facebook/sapling/issues/806
* https://github.com/facebook/sapling/issues/804

Pull Request resolved: https://github.com/facebook/sapling/pull/807

Differential Revision: D52575911

Pulled By: quark-zju

fbshipit-source-id: b24e1a21493f18a06355c984a72936cd11fef2ea
2024-01-18 08:29:13 -08:00
..
create-release.sh create code generator for GitHub actions 2022-08-30 15:37:50 -07:00
gen_workflows.py Add a devcontainer config (#807) 2024-01-18 08:29:13 -08:00
retry.sh create code generator for GitHub actions 2022-08-30 15:37:50 -07:00
tag-name.sh fix compatibility with PEP 440 (#606) 2023-04-18 10:12:23 -07:00
TARGETS eden 2023-10-23 09:12:58 -07:00
verify_release.sh Verify ISL works in a release build. 2022-09-15 18:16:22 -07:00