> For the complete documentation index, see [llms.txt](https://bastion.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bastion.gitbook.io/docs/developers/contributing-guidelines.md).

# Contributing Guidelines

Contributions to Bastion include code, design, documentation, ideas, bug reports, answering user questions, running the project's infrastructure, and advocating for all types of Bastion users.

Bastion welcomes all contributions from anyone willing to work in good faith with other contributors and the community. No contribution is too small and all contributions are valued.

## Issues

Issues in Bastion's repositories are the primary means by which bug reports and feature requests/suggestions are made.

Read the details here:

{% content-ref url="/pages/BkX43d5lAE7OftZojgNF" %}
[Issues](/docs/developers/contributing-guidelines/issues.md)
{% endcontent-ref %}

## Pull Requests

Pull Requests are the way concrete changes are made to the code, documentation, design, dependencies, and tools contained in Bastion's repositories.

Read the details here:

{% content-ref url="/pages/I5YE8Uuwnsv0FjUv2rR8" %}
[Pull Requests](/docs/developers/contributing-guidelines/pulls.md)
{% endcontent-ref %}

## Translations

We want to deliver Bastion and all its services in many different languages from different regions. If you want to contribute on translations and bring it to the world, you can start doing that on Crowdin.

{% embed url="<https://crowdin.com/project/bastion>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://bastion.gitbook.io/docs/developers/contributing-guidelines.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.