Skip to content

Conversation

Angelfirenze01
Copy link

I'd like to edit the punctuation and grammar on this project but I didn't see an immediate way to do so. If I fork this project and clone it before pulling it down to my hard drive, will I be able to individually edit the files?

titanous and others added 30 commits December 22, 2008 06:34
Signed-off-by: Scott Chacon <schacon@gmail.com>
Signed-off-by: Scott Chacon <schacon@gmail.com>
…/javascript as is proper

Signed-off-by: Scott Chacon <schacon@gmail.com>
Signed-off-by: Scott Chacon <schacon@gmail.com>
Signed-off-by: Scott Chacon <schacon@gmail.com>
Signed-off-by: Scott Chacon <schacon@gmail.com>
-- check binary
- attr_reader from, to (I refer to commit sha1.)

Signed-off-by: Scott Chacon <schacon@gmail.com>
usage: git.log(30).skip(10).to_a

Signed-off-by: Scott Chacon <schacon@gmail.com>
- ecc0ce5
- 499758f

Signed-off-by: Scott Chacon <schacon@gmail.com>
Signed-off-by: Scott Chacon <schacon@gmail.com>
add $VERBOSE = true for the tests
…* exist?)

Note: I'm not entirely sure if this is the correct fix, however, it fixes errors in the test suite, and I'll assume completeness on the part of the tests.
Signed-off-by: elliottcable <github.com@elliottcable.com>
TJ Biddle and others added 28 commits January 12, 2015 15:03
When a submodule is cloned into another project, it has a different structure:

The .git folder is well, not a folder, it is a file that's sole contents
include a reference to where the .git folder for the submodule is on the
local drive.

Take that information from the .git *file* and then build our repository
and index location out of this.
…GIT_SSH env value unless a custom value is set via `Git.configure`

closes #212
v1.2.8 allowed setting of GIT_SSH to point to SSH wrapper; v1.2.9
overrides this with value of Git::Base.config.git_ssh.

This is our story in our backlog: https://www.pivotaltracker.com/story/show/86059268.

Signed-off-by: Frank Kotsianas <frankkotsianas@gmail.com>
Fix the encoding issue - 'split': invalid byte sequence in UTF-8 (up-to-date!!)

closes #190
Dropping ruby 1.8.x support
Updated Travis badge
* Fixed unit tests to run again

There were a few issues:

- The `tar xvpf` approach didn't work for me locally, supposedly since I run macOS, where `tar` prints its output to `stderr` by default. The workaround is to redirect `stderr` to `stdout` while running the command.
- The `tar` output also looked a bit different than before, so I changed it to use regexp matching instead of exact string matching (which is more fragile and prone to breakage.)
- The `parent.parent` stuff apparently returns different values now than before. I have really no clue why, but: I think it's better to accept that fact and merge this, so we can start validating the changes people have suggested now.

* Use JRuby 9

We are seeing test failures on JRuby 1.8 and 1.9 mode, and this is using an EOL JRuby anyway. Let's drop these versions in Travis now, and go with JRuby 9k instead. We still _support_ these older JRuby versions until 2.0 is released, when we should also drop Ruby 1.9, 2.0 and 2.1 support.
@perlun
Copy link
Contributor

perlun commented Feb 28, 2018

This PR seems to have the branches messed up; it tries to merge things into some test branch that I don't know what it is. @Angelfirenze01, thanks for the effort. Sorry for the lack of feedback, the project has been largely abandoned for a long time. If you're still interested in helping out, please submit a new PR with your suggested changes (based on the now-current master.)

@perlun perlun closed this Feb 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.