mirror of
https://github.com/FreshRSS/FreshRSS.git
synced 2026-09-22 11:06:27 -04:00
* Fix all broken links in the entire repository * Update docs/CHANGELOG-old2.md Co-authored-by: Alexandre Alapetite <alexandre@alapetite.fr> * Update config.default.php Co-authored-by: Alexandre Alapetite <alexandre@alapetite.fr> * Update README.md Co-authored-by: Alexandre Alapetite <alexandre@alapetite.fr> * Update docs/i18n/freshrss.fr.po Co-authored-by: Alexandre Alapetite <alexandre@alapetite.fr> * Update docs/i18n/templates/freshrss.pot Co-authored-by: Alexandre Alapetite <alexandre@alapetite.fr> * Update README.md Co-authored-by: Alexandre Alapetite <alexandre@alapetite.fr> * Update docs/fr/users/01_Installation.md Co-authored-by: Alexandre Alapetite <alexandre@alapetite.fr> * Update docs/fr/users/01_Installation.md Co-authored-by: Alexandre Alapetite <alexandre@alapetite.fr> * Update docs/en/internationalization.md Co-authored-by: Alexandre Alapetite <alexandre@alapetite.fr> * Manual fixes, preferences * Prefer canonical when known, prefer shorter, prefer roots, prefer URLs with content negotation (e.g. language preference) * Keep 302, 307 unchanged * Use only `.example`, `example.net` or similarly reserved domains for URL examples * Fix language negotiation for developer.mozilla.org * Restore a Stackoverflow 302 * Fix some example.com --------- Co-authored-by: Alexandre Alapetite <alexandre@alapetite.fr>
1.4 KiB
1.4 KiB
Branching
Basic
If you are new to Git, here are some of the resources you might find useful:
- GitHub’s blog post
- https://docs.github.com/en/github/getting-started-with-github/set-up-git
- https://rogerdudler.github.io/git-guide/
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).