• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

bradleyfalzon / gopherci
61%
master: 61%

Build:
Build:
LAST BUILD BRANCH: review-no-approve
DEFAULT BRANCH: master
Repo Added 22 Oct 2016 12:03PM UTC
Files 0
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH push
branch: push
CHANGE BRANCH
x
Reset
  • push
  • analyser-composition
  • build-summary
  • builddb
  • clone-path
  • commit-comment
  • debug
  • disable-private
  • docker
  • docs-errors
  • dominikh
  • dual-comments
  • error-handling
  • failed-diff
  • first-commit
  • fix-goveralls
  • fix-hardcoded
  • gcppubsub
  • godep
  • gopherci-env
  • gopherci.yml
  • graceful
  • ignore-gen
  • integration-test
  • logger
  • master
  • maxcommments
  • memlimit
  • msgs
  • pr-reviews
  • pr-reviews-default
  • preflight
  • pubsub-breaking
  • pubsub-timeout
  • refactor-analyser
  • reference-failures
  • refreader
  • remove-accountid
  • reporter
  • requeue
  • review-no-approve
  • senderid
  • show-env
  • syncronize
  • test
  • various
  • wbsecret
  • webui

pending completion
137

push

travis-ci

bradleyfalzon
Support GitHub PushEvent

This is accomplished with a few refactors.

We no longer fetch the diff URL provided in a Pull Request event,
it was convenient, but it's not available in Pushes and we can
easily calculate it ourselves without the need for the extra
lookup. This was GitHub specific too, other providers may not have
provided that URL.

Analyse does need to process a Push differently than a Pull Request,
and this is managed by the EventType type.

We ignore the GitHub push event's Before SHA ref, during testing
force pushes, this would be the ref of the commit that's being
"overwritten" so it wouldn't exist when clonsed. Unlike a
non-forced push, where the commit exists after the clone. So instead
of using Before, we use After~len(Commits), so no matter how many
commits are being pushed, or whether the previous commit exists or
not, we should be able to process it.

Resolves #27.

118 of 118 new or added lines in 4 files covered. (100.0%)

533 of 875 relevant lines covered (60.91%)

1.55 hits per line

Relevant lines Covered
Build:
Build:
875 RELEVANT LINES 533 COVERED LINES
1.55 HITS PER LINE
Source Files on push
  • List 0
  • Changed 2
  • Source Changed 1
  • Coverage Changed 2
Coverage ∆ File Lines Relevant Covered Missed Hits/Line

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
137 push Support GitHub PushEvent This is accomplished with a few refactors. We no longer fetch the diff URL provided in a Pull Request event, it was convenient, but it's not available in Pushes and we can easily calculate it ourselves without the need f... push 04 Feb 2017 10:34AM UTC bradleyfalzon travis-ci pending completion  
134 push Support GitHub PushEvent This is accomplished with a few refactors. We no longer fetch the diff URL provided in a Pull Request event, it was convenient, but it's not available in Pushes and we can easily calculate it ourselves without the need f... push 04 Feb 2017 03:46AM UTC bradleyfalzon travis-ci pending completion  
133 push Support GitHub PushEvent This is accomplished with a few refactors. We no longer fetch the diff URL provided in a Pull Request event, it was convenient, but it's not available in Pushes and we can easily calculate it ourselves without the need f... push 04 Feb 2017 03:22AM UTC bradleyfalzon travis-ci pending completion  
131 push Support GitHub PushEvent push 04 Feb 2017 03:11AM UTC bradleyfalzon travis-ci pending completion  
See All Builds (294)
  • Repo on GitHub
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc