Files
FreshRSS/docs/en/developers/02_GitHub.md
dependabot[bot] 7d86cbe804 Bump markdownlint-cli from 0.44.0 to 0.45.0 (#7632)
* Bump markdownlint-cli from 0.44.0 to 0.45.0

Bumps [markdownlint-cli](https://github.com/igorshubovych/markdownlint-cli) from 0.44.0 to 0.45.0.
- [Release notes](https://github.com/igorshubovych/markdownlint-cli/releases)
- [Commits](https://github.com/igorshubovych/markdownlint-cli/compare/v0.44.0...v0.45.0)

---
updated-dependencies:
- dependency-name: markdownlint-cli
  dependency-version: 0.45.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* Fix Markdown

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Alexandre Alapetite <alexandre@alapetite.fr>
2025-06-01 22:50:58 +02:00

1.4 KiB
Raw Blame History

Branching

Basic

If you are new to Git, here are some of the resources you might find useful:

Getting the latest code from the FreshRSS repository

First you need to add the official repo to your remote repo list:

git remote add upstream git@github.com:FreshRSS/FreshRSS.git

You can verify the remote repo is successfully added by using:

git remote -v show

Now you can pull the latest development code:

git checkout edge
git pull upstream edge

Starting a new development branch

git checkout -b my-development-branch

Sending a patch

# Add the changed file, here actualize_script.php
git add app/actualize_script.php
# Commit the change and write a proper commit message
git commit
# Double check all looks well
git show
# Push it to your fork
git push

Now you can create a PR based on your branch.

How to write a commit message

A commit message should succinctly describe the changes on the first line. For example:

Fix broken icon

If necessary, this can be followed by a blank line and a longer explanation.

For further tips, see here (chris.beams.io).