Skip to content

Commit 30eaed8

Browse files
authored
chore(maintenance): remove cloud dev environment configurations (#4896)
1 parent 58a7093 commit 30eaed8

4 files changed

Lines changed: 2 additions & 91 deletions

File tree

.devcontainer/Dockerfile

Lines changed: 0 additions & 14 deletions
This file was deleted.

.devcontainer/devcontainer.json

Lines changed: 0 additions & 28 deletions
This file was deleted.

CONTRIBUTING.md

Lines changed: 1 addition & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,6 @@
55
- [Reporting Bugs/Feature Requests](#reporting-bugsfeature-requests)
66
- [Contributing via Pull Requests](#contributing-via-pull-requests)
77
- [Dev setup](#dev-setup)
8-
- [Gitpod](#gitpod)
9-
- [GitHub Codespaces](#github-codespaces)
10-
- [Local environment](#local-environment)
118
- [Sending a pull request](#sending-a-pull-request)
129
- [Local documentation](#local-documentation)
1310
- [Conventions](#conventions)
@@ -80,27 +77,7 @@ timeline
8077

8178
### Dev setup
8279

83-
Firstly, [fork the repository](https://github.com/aws-powertools/powertools-lambda-typescript/fork).
84-
85-
To setup your development environment, we recommend using our pre-configured Cloud environment like Gitpod or GitHub Codespaces.
86-
87-
#### Gitpod
88-
89-
To start using Gitpod, copy the following URL and replace `YOUR_USERNAME` with your GitHub username or organization:
90-
91-
```text
92-
https://gitpod.io/#https://github.com/YOUR_USERNAME/aws-lambda-powertools-typescript
93-
```
94-
95-
This will allow the Cloud environment to target your fork correctly.
96-
97-
#### GitHub Codespaces
98-
99-
To start using GitHub Codespaces, navigate to your fork of the repository, then click on the green `Code` button, and select `Create codespace on <branch_name>` under the `Codespaces` tab (where `<branch_name>` is the branch you want to work on).
100-
101-
#### Local environment
102-
103-
Alternatively, you can use `npm run setup-local` on your local machine.
80+
Firstly, [fork the repository](https://github.com/aws-powertools/powertools-lambda-typescript/fork), then use `npm run setup-local` on your local machine to install all dependencies and setup pre-commit hooks.
10481

10582
### Sending a pull request
10683

docs/contributing/setup.md

Lines changed: 1 addition & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ graph LR
2222
!!! question "First time contributing to an open-source project ever?"
2323
Read this [introduction on how to fork and clone a project on GitHub](https://docs.github.com/en/get-started/quickstart/contributing-to-projects){target="_blank" rel="nofollow"}.
2424

25-
Unless you're using the pre-configured Cloud environment, you'll need the following installed:
25+
You'll need the following installed:
2626

2727
* [GitHub account](https://github.com/join){target="_blank" rel="nofollow"}. You'll need to be able to fork, clone, and contribute via pull request.
2828
* [Node.js 24.x](https://nodejs.org/download/release/latest-v24.x/){target="_blank" rel="nofollow"}. The repository contains an `.nvmrc` file, so if you use tools like [nvm](https://github.com/nvm-sh/nvm#nvmrc), [fnm](https://github.com/Schniz/fnm) you can switch version quickly.
@@ -35,32 +35,8 @@ Unless you're using the pre-configured Cloud environment, you'll need the follow
3535
* [AWS Account bootstrapped with CDK](https://docs.aws.amazon.com/cdk/v2/guide/bootstrapping.html){target="_blank"}
3636
* [AWS CLI installed and configured](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html)
3737

38-
## Cloud environment
39-
40-
!!! warning "A word of caution"
41-
Before using one of the services below check out their pricing.
42-
You can find more information about each service pricing respectively on [Gitpod](https://www.gitpod.io/pricing){target="_blank" rel="nofollow"} and [GitHub Codespaces](https://docs.github.com/en/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces){target="_blank" rel="nofollow"} pages.
43-
44-
Once provisioned, each Cloud environment will come with all development dependencies and tools you'll need to contribute already installed.
45-
46-
### Gitpod
47-
48-
To use a pre-configured Gitpod environment, create or login to a Gitpod account, then replace `YOUR_USERNAME` with your GitHub username or organization.
49-
50-
```bash
51-
https://gitpod.io/#https://github.com/YOUR_USERNAME/powertools-lambda-typescript #(1)!
52-
```
53-
54-
1. For example, if your username is `octocat`, then the final URL should be `https://gitpod.io/#https://github.com/octocat/powertools-lambda-typescript`
55-
56-
### GitHub Codespaces
57-
58-
To use a pre-configured GitHub Codespaces environment, navigate to your fork of the repository, then click on the green `Code` button, and select `Create codespace on <branch_name>` under the `Codespaces` tab (where `<branch_name>` is the branch you want to work on).
59-
6038
## Local environment
6139

62-
> Assuming you've got all [requirements](#requirements).
63-
6440
You can use `npm run setup-local` to install all dependencies locally and setup pre-commit hooks.
6541

6642
!!! note "Curious about what `setup-local` does under the hood?"

0 commit comments

Comments
 (0)