# Target workflow

It is very common for many Github workflows to involve:

1. (Optional) Creating a fork of a repository
2. Working on a feature/bug fix on a feature branch
3. Pushing the feature branch to Github
4. Creating a pull request of the feature branch to the main branch of the repository
5. Have some set of tests and automated checks start to verify the state of the pull request

We are going to replicate this workflow on the example application.

To avoid being overwhelmed with tasks, let's break down the "expected set of tests and automated checks" to be the following:

1. Run unit tests (`calculator.test.ts`)
2. Lint

Then, once the pull request is merged in `main`, we also want to (3) deploy it to Github Pages.


---

# 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://wiki.nushackers.org/hackerschool/ci-cd-with-github-actions/basics-of-github-actions/target-workflow.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.