# 1build

![1build](https://github.com/gopinath-langote/1build/blob/master/docs/assets/1build-logo.png?raw=true)

&#x20;[![1build Version](https://img.shields.io/github/release/gopinath-langote/1build?label=version)](https://github.com/gopinath-langote/1build/releases/latest) [![License](https://img.shields.io/github/license/gopinath-langote/1build)](https://github.com/gopinath-langote/1build/blob/master/LICENSE) [![Build Status](https://travis-ci.org/gopinath-langote/1build.svg?branch=master)](https://travis-ci.org/gopinath-langote/1build) [![Go Report Card](https://goreportcard.com/badge/github.com/gopinath-langote/1build)](https://goreportcard.com/report/github.com/gopinath-langote/1build) ![GitHub followers](https://img.shields.io/github/followers/gopinath-langote?label=Follow\&style=social) ![GitHub stars](https://img.shields.io/github/stars/gopinath-langote/1build?style=social)

**1build is an automation tool that arms you with the convenience to configure project-local command line aliases** – and then run the commands quickly and easily. It is particularly helpful when you deal with multiple projects and switch between them all the time. It is often the fact that different projects use different build tools and have different environment requirements – and then switching from one project to another is becoming increasingly cumbersome. That is where 1build comes into play.

With 1build you can create simple and easily memorable command aliases for commonly used project commands such as build, test, run or anything else. These aliases will have a project-local scope which means that they will be accessible only within the project directory. This way you can unify all your projects to build with the same simple command disregarding of what build tool they use. It will remove the hassle of remembering all those commands improving the mental focus for the things that actually matter.

{% embed url="<https://github.com/gopinath-langote/1build>" %}


---

# 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://1build.gitbook.io/1build/master.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.
