Rebase wrapper #332

Merged
ezwiebel merged 10 commits from rebase-wrapper into master 2017-04-13 13:50:42 -05:00
2 changed files with 72 additions and 20 deletions
Showing only changes of commit adc3a4bd89 - Show all commits

View File

@ -5,7 +5,6 @@ package git
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
*/
import "C"
import (
"errors"
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
"runtime"
"unsafe"
)
@ -43,7 +42,53 @@ func newRebaseOperationFromC(c *C.git_rebase_operation) *RebaseOperation {
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
}
// RebaseOptions are used to tell the rebase machinery how to operate
type RebaseOptions struct{}
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
type RebaseOptions struct {
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
Version uint
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
Quiet int
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
InMemory int
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
RewriteNotesRef string
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
MergeOptions MergeOptions
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
CheckoutOptions CheckoutOpts
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
}
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
// DefaultRebaseOptions returns a RebaseOptions with default values.
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
func DefaultRebaseOptions() (RebaseOptions, error) {
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
opts := C.git_rebase_options{}
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
runtime.LockOSThread()
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
defer runtime.UnlockOSThread()
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
ecode := C.git_rebase_init_options(&opts, C.GIT_REBASE_OPTIONS_VERSION)
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
if ecode < 0 {
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
return RebaseOptions{}, MakeGitError(ecode)
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
}
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
return rebaseOptionsFromC(&opts), nil
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
}
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
func rebaseOptionsFromC(opts *C.git_rebase_options) RebaseOptions {
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
return RebaseOptions{
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
Version: uint(opts.version),
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
Quiet: int(opts.quiet),
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
InMemory: int(opts.inmemory),
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
RewriteNotesRef: C.GoString(opts.rewrite_notes_ref),
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
MergeOptions: mergeOptionsFromC(&opts.merge_options),
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
CheckoutOptions: checkoutOptionsFromC(&opts.checkout_options),
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
}
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
}
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
func (ro *RebaseOptions) toC() *C.git_rebase_options {
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
if ro == nil {
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
return nil
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
}
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
return &C.git_rebase_options{
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
version: C.uint(ro.Version),
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
quiet: C.int(ro.Quiet),
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
inmemory: C.int(ro.InMemory),
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
rewrite_notes_ref: C.CString(ro.RewriteNotesRef),
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
merge_options: *ro.MergeOptions.toC(),
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
checkout_options: *ro.CheckoutOptions.toC(),
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
}
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
}
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
// Rebase object wrapper for C pointer
type Rebase struct {
@ -55,11 +100,6 @@ func (r *Repository) RebaseInit(branch *AnnotatedCommit, upstream *AnnotatedComm
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
runtime.LockOSThread()
defer runtime.UnlockOSThread()
//TODO : use real rebase_options
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
if opts != nil {
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
return nil, errors.New("RebaseOptions Not implemented yet, use nil for default opts")
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
}
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
if branch == nil {
branch = &AnnotatedCommit{ptr: nil}
}
@ -73,7 +113,7 @@ func (r *Repository) RebaseInit(branch *AnnotatedCommit, upstream *AnnotatedComm
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
}
var ptr *C.git_rebase
err := C.git_rebase_init(&ptr, r.ptr, branch.ptr, upstream.ptr, onto.ptr, nil)
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
err := C.git_rebase_init(&ptr, r.ptr, branch.ptr, upstream.ptr, onto.ptr, opts.toC())
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
if err < 0 {
return nil, MakeGitError(err)
}
@ -86,13 +126,8 @@ func (r *Repository) RebaseOpen(opts *RebaseOptions) (*Rebase, error) {
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
runtime.LockOSThread()
defer runtime.UnlockOSThread()
//TODO : use real rebase_options
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
if opts != nil {
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
return nil, errors.New("RebaseOptions Not implemented yet, use nil for default opts")
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
}
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
var ptr *C.git_rebase
err := C.git_rebase_open(&ptr, r.ptr, nil)
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
err := C.git_rebase_open(&ptr, r.ptr, opts.toC())
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
if err < 0 {
return nil, MakeGitError(err)
}
@ -198,9 +233,3 @@ func newRebaseFromC(ptr *C.git_rebase) *Rebase {
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
runtime.SetFinalizer(rebase, (*Rebase).Free)
return rebase
}
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
/* TODO -- Add last wrapper services and manage rebase_options
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
int git_rebase_init_options(git_rebase_options *opts, unsigned int version);
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
*/
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done

carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:42:19 -05:00 (Migrated from github.com)
Review

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.

This describes the structure mechanically, but almost everything is a wrapper, if we're going to have a comment here, it should describe the object itself and/or what you can do with it.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:43:23 -05:00 (Migrated from github.com)
Review

We have prior art of naming git_repository_init() as InitRepository() since the namespacing in C and Go is bit different, so this should be called InitRebase().

We have prior art of naming `git_repository_init()` as `InitRepository()` since the namespacing in C and Go is bit different, so this should be called `InitRebase()`.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:44:06 -05:00 (Migrated from github.com)
Review

Like with the init function, this should be called OpenRebase(). The documentation shouldn't reference the C function git_rebase_init but our own.

Like with the init function, this should be called `OpenRebase()`. The documentation shouldn't reference the C function `git_rebase_init` but our own.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:45:41 -05:00 (Migrated from github.com)
Review

This return value does not match how Go reports errors. I would expect a uint to return the current operation and an error to return any errors.

This return value does not match how Go reports errors. I would expect a `uint` to return the current operation and an `error` to return any errors.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:46:46 -05:00 (Migrated from github.com)
Review

There is no GIT_REBASE_OPERATION_EXEC in git2go, it's RebaseOperationExec.

There is no `GIT_REBASE_OPERATION_EXEC` in git2go, it's `RebaseOperationExec`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:47:37 -05:00 (Migrated from github.com)
Review

There is no git_rebase_next in git2go, we have Next().

There is no `git_rebase_next` in git2go, we have `Next()`.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:50:26 -05:00 (Migrated from github.com)
Review

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.

Missing space. The pointer isn't public so let's not mention it. "unmanaged resources" covers whatever we decide to put in there.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
carlosmn commented 2016-10-31 14:54:32 -05:00 (Migrated from github.com)
Review

The other public id fields are named Id.

The other public id fields are named `Id`.
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:57:15 -05:00 (Migrated from github.com)
Review

Ok, I followed go convention suggested by my IDE plugin

Ok, I followed go convention suggested by my IDE plugin
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:38 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:42 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 18:58:49 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:02 -05:00 (Migrated from github.com)
Review

Done.
I also added ErrClassRebase in git.go
Hope this is correct

Done. I also added `ErrClassRebase` in `git.go` Hope this is correct
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:09 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done
ezwiebel commented 2016-10-31 19:01:27 -05:00 (Migrated from github.com)
Review

Done

Done

View File

@ -9,6 +9,29 @@ import (
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
// Tests
func TestDefaultRebaseOptions(t *testing.T) {
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
opts, err := DefaultRebaseOptions()
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
checkFatal(t, err)
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
if opts.Version != 1 {
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
t.Error("Expected opts Version to equal 1, got ", opts.Version)
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
}
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
if opts.Quiet != 0 {
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
t.Error("Expected opts Quiet to equal 1, got ", opts.Quiet)
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
}
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
if opts.InMemory != 0 {
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
t.Error("Expected opts InMemory to equal 1, got ", opts.InMemory)
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
}
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
if opts.RewriteNotesRef != "" {
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
t.Error("Expected opts RewriteNotesRef to equal 1, got ", opts.RewriteNotesRef)
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
}
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
copts := opts.toC()
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
if copts == nil {
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
t.Error("Copts should not be nil")
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
}
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
}
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
func TestRebaseAbort(t *testing.T) {
// TEST DATA

carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
carlosmn commented 2016-10-31 14:56:01 -05:00 (Migrated from github.com)
Review

Don't hard-code 1 here, the point of the version field is to increase it.

Don't hard-code 1 here, the point of the version field is to increase it.
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
ezwiebel commented 2016-10-31 19:03:04 -05:00 (Migrated from github.com)
Review

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a #define or a constant that was used as default version number.
The test doesn't have great value though

Not sure how to handle this. It's a test that checks the default version returned by DefaultRebaseOptions. After a look into C code, I thought it was a `#define` or a constant that was used as default version number. The test doesn't have great value though
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
carlosmn commented 2016-11-13 12:33:45 -06:00 (Migrated from github.com)
Review

The version it needs to return in the version that is specified by the libgit2 headers in the #define. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.

The version it needs to return in the version that is specified by the libgit2 headers in the `#define`. That's what the compiler is building and that's what it will use in order to figure out the size of the struct, which has to match what we're telling libgit2 we have.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.
ezwiebel commented 2016-11-14 02:13:44 -06:00 (Migrated from github.com)
Review

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.

Thanks for that. However I'm not sure how I should do as the cgo feature seems to be forbidden in tests... I will just drop this very low value test I think.