# Features — go_api

Evidence date: 2026-10-13. Source: `git@bitbucket.org:overdrive/go_api.git`, `master` at `366442a` (2023-09-18). Full hash `366442ae98ef4d7180c587e01ebb2fdbe09c1fe5`.

Status words used here:

- **Current** — present on `master` at `366442a`.
- **Stub** — the file describes the feature, and the behaviour cannot analyse an application from this tree.
- **Not in git** — named by the repository slug or the task-creation scan, and no file exists at that path.

There are three commits and one branch. Nothing in git history is a removed feature. No feature is marked in-development by a branch, ticket, or TODO in the tree. Whether a pipeline run on `master` succeeds against a live Sonar server is **Unknown / Requires Confirmation**.

## Current

### Repository scaffold

| Feature | Location | Notes |
|---|---|---|
| Default ignore list | `.gitignore` | Bitbucket's example list, added in `14e18c6` (2023-09-18, Jaco Brits). Header says to customize it. It still matches that template. |
| Sonar project key | `sonar-project.properties` | Added in `5c622e7` (2023-09-18, Jaco Brits). One property: `sonar.projectKey=overdrive_go_api_AYqpslFAuNwRc2P2S9SL`. |
| Pipeline definition | `bitbucket-pipelines.yml` | Added in `366442a` (2023-09-18, Jaco Brits). Image `maven:3.3.9`. Bound to branch pattern `{master}`. |

## Stub

These are written in the pipeline. They do not build or serve an application from the current tree.

### SonarQube analysis

| Feature | Location | Notes |
|---|---|---|
| Step "SonarQube analysis" | `bitbucket-pipelines.yml` | Anchor `&build-step`. The only step. |
| Pipe `sonarsource/sonarqube-scan:2.0.1` | Same step | Passes `SONAR_HOST_URL` and `SONAR_TOKEN` from pipeline variables. |
| Full clone | `clone.depth: full` | History is cloned. No other clone option is set. |
| Branch pattern `{master}` | `pipelines.branches` | The repository's only branch is `master`. No `default` or `pull-requests` pipeline. |
| Sonar cache definition | `definitions.caches.sonar` = `~/.sonar` | The step does not list `caches:`. The cache is declared and not attached. |

The script does not call `mvn`, `go`, or a test runner. There is no `pom.xml` and no `go.mod`. Provenance: **Implemented** in the YAML.

## Not in git

| Name | Why it is listed |
|---|---|
| `sonarqube_scan.bat` | Task-creation scan of the scan-host tree. Absent from all three commits. |
| Go API: `go.mod`, `go.sum`, `.go` sources, routes | Suggested by the repository slug. Not committed. |
| `README.md` | Not committed. |
| Tests, lint config, Docker, app config | Not committed. |
| `pom.xml` | Implied by the Maven image only. Not committed. The script does not run Maven. |

## Planned

No planned feature is written in the repository. There is no backlog, TODO, or ticket reference in the tree.

The pipeline comments tell the reader to take `SONAR_HOST_URL` and `SONAR_TOKEN` from repository or workspace variables, and not to put the token in clear text. Those are instructions on the existing step, not a product plan.

## In development

No branch other than `master`. No uncommitted source was in the clone used for this inspection (`git status` clean on `366442a` after clone).

## Recently changed

The repository was created and finished on 2023-09-18, in this order: `.gitignore`, then `sonar-project.properties`, then `bitbucket-pipelines.yml`. No commit since that date.

## Deprecated / removed

Git history does not delete a feature. There is no deprecated path, flag, or replacement stack.

## Tests as a feature

No test file, test script, or test step exists. `.gitignore` ignores `TEST*.xml` because that pattern is in the stock Bitbucket template, not because a test suite is configured.