Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: dogestry/dogestry
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.4.0
Choose a base ref
...
head repository: dogestry/dogestry
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.4.1
Choose a head ref
  • 7 commits
  • 5 files changed
  • 6 contributors

Commits on Mar 10, 2015

  1. Bump up version from 1.3.0 to 1.4.0

    Didip Kerabat committed Mar 10, 2015
    Configuration menu
    Copy the full SHA
    d06b6c6 View commit details
    Browse the repository at this point in the history

Commits on Apr 10, 2015

  1. Update Readme.md

    @alicegoldfuss
    alicegoldfuss committed Apr 10, 2015
    Configuration menu
    Copy the full SHA
    3f5c1ea View commit details
    Browse the repository at this point in the history

Commits on Apr 14, 2015

  1. Update Readme.md

    @alicegoldfuss
    alicegoldfuss committed Apr 14, 2015
    Configuration menu
    Copy the full SHA
    31bf983 View commit details
    Browse the repository at this point in the history

  2. Always export metadata during push. 

    Fixes #46.
    @toffer
    toffer committed Apr 14, 2015
    Configuration menu
    Copy the full SHA
    4761063 View commit details
    Browse the repository at this point in the history

Commits on Apr 16, 2015

  1. Merge pull request #47 from dogestry/always-push-metadata 

    Always export metadata during push.
    @didip
    didip committed Apr 16, 2015
    Configuration menu
    Copy the full SHA
    c44b6f6 View commit details
    Browse the repository at this point in the history

Commits on Apr 22, 2015

  1. Clean up the wait logic. Always push something into the channel. 

    By always putting something into the channel we can remove all
the waitgroups and we don't run any risk of missing stuff. It
seems that in some cases the last entry in the channel was getting
missed when it was closed.
    @relistan
    relistan committed Apr 22, 2015
    Configuration menu
    Copy the full SHA
    4630cc6 View commit details
    Browse the repository at this point in the history

  2. Merge pull request #51 from dogestry/wait-for-things 

    Clean up the wait logic. Always push something into the channel.
    @relistan
    relistan committed Apr 22, 2015
    Configuration menu
    Copy the full SHA
    64fb1d3 View commit details
    Browse the repository at this point in the history
Loading