From f035e0f2044b0cc9fbdd755ac11af53d9848c324 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jes=C3=BAs=20Silva?= <79662866+JesusSilvaUtrera@users.noreply.github.com> Date: Mon, 13 Jan 2025 14:02:24 +0100 Subject: [PATCH] Fix link to DEVELOPING.md (#457) ### Proposed changes This PR just changes a broken link on the docs that was pointing to a `GETTING_STARTED.md` file that doesn't exist anymore. The Table of Content of the file was updated automatically when saving. Signed-off-by: JesusSilvaUtrera --- CONTRIBUTING.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c3009b7ab..46b684f0d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -19,6 +19,8 @@ All types of contributions are encouraged and valued. See the [Table of Contents - [Reporting Bugs](#reporting-bugs) - [Requesting Features](#requesting-features) - [Your First Code Contribution](#your-first-code-contribution) + - [A Primer On Project Workflow](#a-primer-on-project-workflow) + - [How Do I Submit a Good Code Contribution?](#how-do-i-submit-a-good-code-contribution) - [Styleguides](#styleguides) ## I Have a Question @@ -121,7 +123,7 @@ This projects adopts a [feature branch workflow](https://about.gitlab.com/topics ```bash git checkout -b /fix-issue-12345 main ``` -1. **Work on your contribution**. See [instructions](GETTING_STARTED.md) on how to get started with Beluga development. +1. **Work on your contribution**. See [instructions](DEVELOPING.md) on how to get started with Beluga development. 1. **Test your changes**. For bug fixes, make sure regression tests are included. 1. **Document your changes as needed**. For new features, make sure added functionality is clearly documented. 1. **Push the branch to your fork on GitHub**.