- 12 6月, 2018 1 次提交
-
-
由 Mislav Marohnić 提交于
-
- 10 6月, 2018 5 次提交
-
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
`go fmt ./...` affects the `vendor/` directory before Go 1.9.
-
由 Mislav Marohnić 提交于
-
- 09 6月, 2018 5 次提交
-
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
This was from the time when we tried to have hub build even if it wasn't checkout out within a local GOPATH. This change assumes a working Go environment.
-
- 08 6月, 2018 6 次提交
-
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
Respect XDG_CONFIG_HOME and XDG_CONFIG_DIRS. https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html#variables Fixes #1048, closes #1061
-
由 Mislav Marohnić 提交于
Full tokens (40 characters) are now allowed as password and tested in a separate scenario.
-
- 07 6月, 2018 18 次提交
-
-
由 Mislav Marohnić 提交于
Add `hub release --format=<FORMAT>` option
-
由 Mislav Marohnić 提交于
Latest build on this branch reports 89.5%: https://travis-ci.org/github/hub/builds/389290940
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
A method to measure code coverage across tests
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
Go has code coverage tooling for test mode, which temporarily rewrites the source code to insert annotations which will activate during the test run and track progress of executed code. Then, upon process completion, that information is dumped into a coverage report. We can't use this approach for hub, at least not without substantial changes. First of all, hub's test coverage is mostly "from the outside", utilizing Cucumber to invoke the binary with different arguments and inspect the outputs and result. There are some tests in go, but they are minimal compared to the cukes. Second, hub frequently aborts the process on errors via `os.Exit(1)`, and those scenarios need to be tested too. However, if the process exits prematurely, the code coverage report will never be generated. To work around this, I first used the go tool that annotates the source: go tool cover -mode=set -var=LiveCoverage myfile.go This injects `LiveCoverage.Count[pos] = 1` lines at appropriate places all over the source code, and generates a mapping of line/column positions in the original source. Then I rewrite those lines to become a method invocation: coverage.Record(LiveCoverage, pos) The new `Record` method will immediately append the information to a code coverage report file as soon as it's invoked. This ensures that there is coverage information even if the process gets aborted. This approach works the same for go tests as well as for cukes. They all append to the same file. Finally, the rest of Go tooling is used to generate an HTML report of code coverage: go tool cover -html=cover.out
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
Since there are multiple Go builds, run it only for the latest Go build. In `.travis.yml`, the latest Go build should appear first in the list.
-
由 Mislav Marohnić 提交于
This avoids polluting the user's home environment. https://github.com/github/hub/pull/1705#issuecomment-392759921
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
Previously, when `:` wouldn't appear in the value for `head`, the GitHub API would ignore the `head` parameter altogether. Now, ensure that `<OWNER>:` syntax is always populated by adding the default from the current repository.
-
由 Mislav Marohnić 提交于
Add installation method for archlinux
-
由 Mislav Marohnić 提交于
-
- 06 6月, 2018 5 次提交
-
-
由 Mislav Marohnić 提交于
Create '--no-edit' option for hub pull-request
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
PR checkout: ensure resulting branch is automatically pushable
-
-
由 Mislav Marohnić 提交于
-