# History, Design and Future { #history-design-and-future }

Some time ago, <a href="https://github.com/fastapi/fastapi/issues/3#issuecomment-454956920" class="external-link" target="_blank">a **FastAPI** user asked</a>:

> What’s the history of this project? It seems to have come from nowhere to awesome in a few weeks [...]

Here's a little bit of that history.

## Alternatives { #alternatives }

# Historia, Diseño y Futuro

Hace algún tiempo, <a href="https://github.com/fastapi/fastapi/issues/3#issuecomment-454956920" class="external-link" target="_blank">un usuario de **FastAPI** preguntó</a>:

> ¿Cuál es la historia de este proyecto? Parece haber surgido de la nada y ser increíble en pocas semanas [...]

Aquí hay un poquito de esa historia.

## Alternativas

Saeye Lee <******@****.***> 1731012374 +0900

				CreateTime: obj.ModTime, // ModTime is createTime for config history entries.
			}
			if withData {
				data, err := readConfig(ctx, objAPI, obj.Name)
				if err != nil {
					// ignore history file if not readable.
					continue
				}

				data, err = decryptData(data, obj.Name)
				if err != nil {
					// ignore history file that cannot be loaded.
					continue
				}

a clear, valuable commit history for our open-source projects. They apply to all contributors, 
fostering efficient reviews and robust code.

## Why Pull Requests?

Pull Requests (PRs) drive quality in MinIO’s codebase by:
- Enabling peer review without pair programming.
- Documenting changes for future reference.
- Ensuring commits tell a clear story of development.

# -u: error if undefined variable used
# -x: log all commands
# -o pipefail: entire command fails if pipe fails. watch out for yes | ...
# -o history: record shell history
# -o allexport: export all functions and variables to be available to subscripts
#               (affects 'source $TFCI')
set -exo pipefail -o history -o allexport

# Set TFCI_GIT_DIR, the root directory for all commands, to two directories

        tracker.setName("name3");
        tracker.transform(responseData);

        List<String> history = tracker.getNameHistory();
        assertEquals(3, history.size());
        assertEquals("name1", history.get(0));
        assertEquals("name2", history.get(1));
        assertEquals("name3", history.get(2));
    }

    /**
     * Test concurrent name access
     */

                display = ParameterDisplay.PROMPT,
                allowEmpty = true,
            )
        }

        cleanup {
            history(days = 180)
        }

        this.init()
    }
}

class PublishFinalRelease(
    branch: VersionedSettingsBranch,
) : PublishRelease(
        promotedBranch = branch.branchName,

### Summary { #summary }

I used to say I didn't like history that much... and look at me now giving "tech history" lessons. 😅

 * See https://www.jetbrains.com/help/teamcity/teamcity-data-clean-up.html#Clean-up+Rules
 *
 * @param historyDays days number of days to store build history .
 * @param artifactsDays number of days to store artifacts. In the stored history, artifacts older than this number will be cleaned up.
 * @param artifactPatterns patterns for artifacts clean-up. If not specified, all artifacts will be removed.
 */