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
We follow conventional commit specification for commit messages. This means that each commit message should start with a type, followed by an optional scope, and then a description. The types we use are:
3
+
- Ensure any code you produce is correct.
4
+
- for commit messages use conventional commit format, e.g. `feat: add new feature`, `fix: correct a bug`, `docs: update documentation`, etc. https://www.conventionalcommits.org/en/v1.0.0/
4
5
5
-
-**feat**: A new feature
6
-
-**fix**: A bug fix
7
-
-**docs**: Documentation only changes
8
-
-**style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
9
-
-**refactor**: A code change that neither fixes a bug nor adds a feature
10
-
-**perf**: A code change that improves performance
11
-
-**test**: Adding missing or correcting existing tests
12
-
-**build**: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
13
-
-**ci**: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
14
-
-**chore**: Other changes that don't modify src or test files
6
+
## New Feature Instructions
15
7
16
-
More details in here https://www.conventionalcommits.org/en/v1.0.0/
8
+
When creating a new feature, follow these steps:
9
+
- Update the README.md to include the new feature in the list of features.
10
+
- Each feature should be implemented under src/feature-name. Include a devcontainer-feature.json and install.sh file.
11
+
- The install.sh file should install the package from the source repository. Not using a package manager like apt.
12
+
- Each feature should have a test under test/feature-name/test.sh
13
+
- Each feature should include a global test under test/_global/feature-name-specific-version.sh if a specific version can be installed.
14
+
- Update the ../../test/_global/all-tools.sh to validate the new feature is installed.
15
+
- Update the ../../test/_global/scenarios.json to include the new feature.
Copy file name to clipboardExpand all lines: README.md
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,7 @@ This repository contains a _collection_ of Features.
8
8
9
9
| Name | URL | Description |
10
10
| --- | --- | --- |
11
+
| bat |https://github.com/sharkdp/bat| A cat(1) clone with syntax highlighting and Git integration. |
11
12
| flux |https://fluxcd.io/flux/installation/| Flux is a tool for keeping Kubernetes clusters in sync with sources of configuration |
12
13
| notation |https://notaryproject.dev/| Notation is a CLI project to add signatures as standard items in the registry ecosystem, and to build a set of simple tooling for signing and verifying these signatures. This should be viewed as similar security to checking git commit signatures, although the signatures are generic and can be used for additional purposes. Notation is an implementation of the Notary v2 specifications.|
13
14
| crane |https://github.com/google/go-containerregistry/blob/main/cmd/crane/README.md| crane is a tool for interacting with remote images and registries.|
@@ -26,6 +27,23 @@ This repository contains a _collection_ of Features.
26
27
27
28
28
29
30
+
### `bat`
31
+
32
+
Running `bat` inside the built container will print the help menu of bat.
0 commit comments