Skip to content

postgrespro/postgres

master_ci
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code
This branch is 1 commit ahead, 6381 commits behind postgres:master.

Latest commit

 

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
doc
 
 
src
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

PostgreSQL mirror

Travis-ci Status Build status

Involves automatic builds of PRs/commits on Linux (Travis-CI) and Windows (Appveyor):

  • Linux: full make check-world
  • Windows: only build + make check

These checks are very similar to cfbot builds.

If you want to verify your patch set before sending it to hackers, then just send a PR with your changes to the branch master_ci from any other postgres fork across GitHub. See example.

Branch master is left intact for convinience. Default branch is master_ci now, but do not push or commit anything there. To update master_ci you should add upstream remote first (you have to do it only once):

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

Then update master branch:

git checkout master
git pull --rebase upstream master
git push -f origin master

And finally update master_ci branch:

git checkout master_ci
git pull --rebase upstream master
git push -f origin master_ci

For original PostgreSQL readme refer to README file.

About

Up-to-date mirror of @postgres with Travis-CI / Appveyor integration and PRs

Resources

Stars

Watchers

Forks

Packages

No packages published

Languages

  • C 83.3%
  • PLpgSQL 6.0%
  • Perl 2.3%
  • C++ 2.2%
  • TSQL 1.7%
  • Yacc 1.4%
  • Other 3.1%