# Contributing Packages

There’s millions of open source projects and `pkgx` needs your help to package\
them up!

{% hint style="success" %}
Visit [github.com/pkgxdev/pantry](https://github.com/pkgxdev/pantry) for the full documentation.
{% endhint %}

{% hint style="info" %}
Curious about a specific pkg? `pkgx bk edit deno` will open deno’s`package.yml` in your editor.
{% endhint %}

## Packagers Who Care

You trust us to just work and make your workflows happen. We take this job\
seriously and we go the extra mile on a per-package basis, for example:

* Our `git` ignores `.DS_Store` files by default
* Our RubyGems defaults to user-installs and ensures gems are in `PATH`
* Our `python` comes unversioned so the huge numbers of scripts that invoke`/usr/bin/env python` actually work
* Our `pyenv` automatically installs the python versions it needs

Additionally, we insist our pkgs are relocatable, which is why we can install in\
your home directory (but this also means you could pick up the whole `~/.pkgx`\
directory and bundle it with your app.) We also begin packaging new releases\
almost immediately as soon as they go live using various automations.

We care about your developer experience, *not ours*.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pkgx.sh/appendix/packaging/pantry.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.