Skip to content

Commit

Permalink
fix links
Browse files Browse the repository at this point in the history
  • Loading branch information
irgolic committed Aug 25, 2023
1 parent a3cf366 commit 817c911
Show file tree
Hide file tree
Showing 5 changed files with 5 additions and 6 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Breathe life into your codebase, configurably

## 🚀 Getting Started

Please see the [installation guide](https://docs.autopr.com/docs/installation).
Please see the [installation guide](https://docs.autopr.com/installing/github).

## 🐞 Known Bugs

Expand Down
2 changes: 1 addition & 1 deletion website/docs/installing/github.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,4 +19,4 @@ Follow these steps to set up AutoPR in your GitHub repository:
3. In your GitHub repository settings, navigate to `Secrets and variables -> Actions` and add your OpenAI API key as `OPENAI_API_KEY`.
4. In your GitHub repository settings, go to `Actions -> General` and scroll down to `Workflow permissions`. Enable `Allow GitHub Actions to create and approve pull requests`.

That's it! Check out the [Customization guide](./customization) to see how to customize AutoPR for your repository.
That's it! Check out the [Configuring guide](../configuring) to see how to customize AutoPR for your repository.
2 changes: 1 addition & 1 deletion website/docs/intro.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ hide_title: true

AutoPR breathes life into your repository with generative AI.

See the [installation guide](./installation) to get started.
See the [installation guide](installing/github) to get started.

## Actions, Workflows and Triggers

Expand Down
4 changes: 2 additions & 2 deletions website/docs/reference/triggers.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,15 +7,15 @@ sidebar_position: 3
Triggers are the sensors of your repository. They monitor for specific events, and once an event
occurs, they initiate a workflow. Let's deep dive into how to write triggers.

**Important**: Before you begin writing a trigger, [set up validation in your editor](setting-up-yaml-schema) for ease of writing.
**Important**: Before you begin writing a trigger, [set up validation in your editor](../tutorials/setting-up-yaml-schema) for ease of writing.

Triggers are located in your `.autopr` configuration directory, as the `.autopr/triggers.yaml` file.
Alternatively, you can also define triggers in the `.autopr/triggers/*.yaml` folder.

## 🧐 Properties of different triggers

Each trigger has the `run` property, which specified the workflow that should be activated when the trigger condition is met.
The `run` property must match the name of either a [default workflow](../workflow-catalogue) or a [custom-defined workflow](writing-a-workflow).
The `run` property must match the name of either a [default workflow](../workflow-catalogue) or a [custom-defined workflow](../tutorials/writing-a-workflow).

They also have the `parameters` property, which is an optional object that contains global variables used in the workflow.
For example, the `parameters` property can be used to define the `FILE_SUMMARY_PROMPT` variable, which is used in the
Expand Down
1 change: 0 additions & 1 deletion website/docusaurus.config.js
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,6 @@ const config = {
projectName: 'AutoPR', // Usually your repo name.
trailingSlash: false,


onBrokenLinks: 'throw',
onBrokenMarkdownLinks: 'warn',

Expand Down

0 comments on commit 817c911

Please sign in to comment.