Go to file
Jacob Heider 50224807cb fix(ruby)
fixes #236
fixes #237
fixes #238
fixes #239
fixes #240
fixes #288
fixes #289
fixes #290
fixes #291
fixes #292
fixes #293
fixes #294
fixes #295
fixes #296
fixes #297
fixes #298
fixes #299
fixes #300
fixes #301
fixes #302
fixes #303
fixes #304
fixes #305
fixes #306
fixes #307
fixes #308
fixes #309
fixes #310
fixes #311
fixes #312
fixes #313
fixes #314
fixes #315
2023-02-13 21:23:02 -05:00
.github don't open issues unless we're on main 2023-02-13 20:14:10 -05:00
.vscode simplify index-packages (#153) 2023-02-02 16:51:19 -05:00
projects fix(ruby) 2023-02-13 21:23:02 -05:00
scripts $HOME is not expanded 2023-02-11 15:46:39 -05:00
.gitignore instructions for tea.xyz/brewkit~0.2 2023-02-13 08:31:29 -05:00
deno.jsonc instructions for tea.xyz/brewkit~0.2 2023-02-13 08:31:29 -05:00
README.md instructions for tea.xyz/brewkit~0.2 2023-02-13 08:31:29 -05:00

tea

This pantry† represents the most essential open source packages in the world. We promise to prioritize fixes, updates and robustness for these packages. We will not lightly accept additions, and thus suggest submitting your pull request against pantry.extra first.

† see pantry.zero for “what is a pantry”

Use with tea/cli

tea/cli clones/updates this pantry and pantry.extra when installed with the installer or when you run tea --sync. At this time pantries are not versioned.

 

Contributing

$ git clone https://github.com/teaxyz/pantry.core

$ cd pantry.core
# all the following commands operate in `./tea.out`
# your tea installation remains untouched

$ pkg init
# ^^ creates a “wip” package.yml

$ pkg edit
# ^^ opens the new package.yml in your EDITOR

$ pkg build
# ^^ will probably require a (zero permissions) GitHub [PAT].
# Using `gh auth login` is the easiest way to set this up.

$ pkg test
# ^^ you need to write a test that verifies the package works

$ gh repo fork
$ git branch -m my-new-package
$ git push origin my-new-package
$ gh pr create

Packaging Guide

Packaging can be cumbersome. Our wiki is our packaging knowledge base. For other assistance, start a discussion.

After Your Contribution

We build “bottles” (tard binaries) and upload them to both our centralized bottle storage and decentralized IPFS.

tea automatically builds new releases of packages as soon as they are released (usually starting the builds within seconds). There is no need to submit PRs for updates.