Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Quick reference guide on fork and pull request workflow
| Date | Stars |
|---|---|
| 2026-07-24 | 962 |
| 2026-07-25 | 962 |
| 2026-07-28 | 962 |
| 2026-07-30 | 962 |
| 2026-08-06 | 962 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
Fork and Pull Request Workflow
==============================
<!-- :: \iffalse -->
[![Download PDF][SHIELD_PDF]][DOWNLOAD_PDF]
[![Download TXT][SHIELD_TXT]][DOWNLOAD_TXT]
[![CC BY 4.0 License][SHIELD_CCBY]][CCBY]
<!-- :: -->
[SHIELD_PDF]: https://img.shields.io/badge/download-PDF-brightgreen.svg
[SHIELD_TXT]: https://img.shields.io/badge/download-TXT-brightgreen.svg
[SHIELD_CCBY]: https://img.shields.io/badge/license-CC%20BY%204.0-blue.svg
[DOWNLOAD_PDF]: https://github.com/susam/gitpr/releases/download/0.6.0/gitpr.pdf
[DOWNLOAD_TXT]: https://github.com/susam/gitpr/releases/download/0.6.0/gitpr.txt
<!-- :: \fi -->
<!-- Version 0.6.0 (2018-11-19) -->
<!-- :: \maketitle -->
This document describes how developers may contribute pull requests to
an upstream repository and how upstream owners may merge pull requests
from contributors according to the very popular fork and pull request
workflow followed in many projects on GitHub.
The download buttons above download version 0.6.0 <!-- x -->
(the latest stable release) of this document. <!-- x -->
<!-- x -->
The most recent version of this document is available at
[git.io/gitpr](https://git.io/gitpr).
<!-- :: \iffalse -->
Contents
--------
* [Introduction](#introduction)
* [Quick Reference](#quick-reference)
* [Create Pull Request](#create-pull-request)
* [Fork and Clone](#fork-and-clone)
* [Work on Pull Request](#work-on-pull-request)
* [Keep Your Fork Updated](#keep-your-fork-updated)
* [Amend Last Commit](#amend-last-commit)
* [Rebase Commits](#rebase-commits)
* [Edit Commits](#edit-commits)
* [Force Push](#force-push)
* [Delete Branch](#delete-branch)
* [Merge Pull Request](#merge-pull-request)
* [Without Merge Commit](#without-merge-commit)
* [With Merge Commit](#with-merge-commit)
* [Nifty Commands](#nifty-commands)
* [Pretty Log](#pretty-log)
* [Staged Diff](#staged-diff)
* [Branch Listing](#branch-listing)
* [More Aliases](#more-aliases)
* [Merge Base](#merge-base)
* [Commit Partial Changes](#commit-partial-changes)
* [Some Git Wisdom](#some-git-wisdom)
* [License](#license)
* [Support](#support)
<!-- :: \fi -->
<!-- :: \tableofcontents -->
<!-- :: \pagebreak -->
Introduction
------------
Every project has a main development branch where the developers push
commits on a day-to-day basis. Usually, the main development branch is
`master` but some projects choose to have `develop` or `trunk` or
another branch for day-to-day development activities. We refer to this
main development branch as the *main development branch* throughout this
document to keep the text general. However in the command examples and
ASCII-diagrams, we use `master` as an example of the main development
branch.
We use the following placeholders in the command examples and
ASCII-diagrams in this document:
- `GITHUB`: [`github.com`](https://github.com/) or domain
name/hostname of your private GitHub Enterprise system.
- `USER` or `CONTRIBUTOR`: The user that forks an upstream repository,
creates pull requests, and sends them to the upstream repository.
- `UPSTREAM-OWNER`: Owner of the upstream repository. This is the name
of the user or organization that merges pull requests into the
upstream repository.
- `REPO`: Repository name.
- `FILES`: One or more filenames to be staged for a commit.
- `TOPIC-BRANCH`: Feature-specific or bug-specific branch where a
contributor develops her or his contribution. This is referred to as
the *topic branch* in the text.
These placeholders should be substituted with appropriate values while
executing the commands presented in this document.
Beginners to this workflow should always remember that a Git branch is
not a container of commits, but rather a lightweight moving pointer that
points to a commit in the commit history.
A---B---C
↑
(master)
When a new commit is made in a branch, its branch pointer simply moves
to point to the last commit in the branch.
A---B---CExcerpt of 27,564 characters
Read on GitHub
44
Would you bet a product on this? Bounded 0–100 and slow moving.
matched fp:34f0a902afbc9faf, topic:workflow