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 53 additions and 20 deletions
Showing only changes of commit 193b21398b - Show all commits

View File

@ -33,7 +33,7 @@ type RebaseOperation 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: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
Exec string Exec string
} }
func rebaseOperationFromC(c *C.git_rebase_operation) *RebaseOperation { 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: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
operation := &RebaseOperation{} operation := &RebaseOperation{}
operation.Type = RebaseOperationType(c._type) operation.Type = RebaseOperationType(c._type)
operation.ID = newOidFromC(&c.id) operation.ID = newOidFromC(&c.id)
@ -50,15 +50,6 @@ type Rebase 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: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
ptr *C.git_rebase ptr *C.git_rebase
} }
// Abort aborts a rebase that is currently in progress, resetting the repository and working directory to their state before rebase began.
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 (rebase *Rebase) Abort() 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
err := C.git_rebase_abort(rebase.ptr)
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 {
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 MakeGitError(err)
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 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
//RebaseInit initializes a rebase operation to rebase the changes in branch relative to upstream onto another branch. //RebaseInit initializes a rebase operation to rebase the changes in branch relative to upstream onto another branch.
func (r *Repository) RebaseInit(branch *AnnotatedCommit, upstream *AnnotatedCommit, onto *AnnotatedCommit, opts *RebaseOptions) (*Rebase, error) { func (r *Repository) RebaseInit(branch *AnnotatedCommit, upstream *AnnotatedCommit, onto *AnnotatedCommit, opts *RebaseOptions) (*Rebase, error) {
runtime.LockOSThread() runtime.LockOSThread()
@ -66,7 +57,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
//TODO : use real rebase_options //TODO : use real rebase_options
if opts != nil { if opts != nil {
return nil, errors.New("RebaseOptions Not implemented yet") 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
} }
if branch == nil { if branch == nil {
@ -90,6 +81,23 @@ 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
return newRebaseFromC(ptr), nil return newRebaseFromC(ptr), nil
} }
// OperationAt gets the rebase operation specified by the given index.
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 (rebase *Rebase) OperationAt(index uint) *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: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
operation := C.git_rebase_operation_byindex(rebase.ptr, C.size_t(index))
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 newRebaseOperationFromC(operation)
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
// CurrentOperationIndex gets the index of the rebase operation that is currently being applied.
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 the first operation has not yet been applied then this returns -1 (C.GIT_REBASE_NO_OPERATION).
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 (rebase *Rebase) CurrentOperationIndex() 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
return int(C.git_rebase_operation_current(rebase.ptr))
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
// OperationCount gets the count of rebase operations that are to be applied.
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 (rebase *Rebase) OperationCount() 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
return uint(C.git_rebase_operation_entrycount(rebase.ptr))
carlosmn commented 2016-10-31 14:40:54 -05:00 (Migrated from github.com)
Review

This looks like it should have a much more generic name, since what it does is unrelated to note rewriting and it's simply mapping an empty string and NULL.

This looks like it should have a much more generic name, since what it does is unrelated to note rewriting and it's simply mapping an empty string and `NULL`.
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:29 -05:00 (Migrated from github.com)
Review

I understand your point. Renamed to mapEmptyStringToNull :p

I understand your point. Renamed to mapEmptyStringToNull :p
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
// Next performs the next rebase operation and returns the information about it. // Next performs the next rebase operation and returns the information about it.
// If the operation is one that applies a patch (which is any operation except GIT_REBASE_OPERATION_EXEC) // If the operation is one that applies a patch (which is any operation except GIT_REBASE_OPERATION_EXEC)
// then the patch will be applied and the index and working directory will be updated with the changes. // then the patch will be applied and the index and working directory will be updated with the changes.
@ -104,7 +112,7 @@ func (rebase *Rebase) Next() (*RebaseOperation, 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
return nil, MakeGitError(err) return nil, MakeGitError(err)
} }
return rebaseOperationFromC(ptr), nil return newRebaseOperationFromC(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
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
} }
// Commit commits the current patch. // Commit commits the current patch.
@ -148,9 +156,16 @@ func (rebase *Rebase) Finish() 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
return nil return nil
} }
// OperationCount gets the count of rebase operations that are to be applied. // Abort aborts a rebase that is currently in progress, resetting the repository and working directory to their state before rebase began.
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 (rebase *Rebase) OperationCount() uint { func (rebase *Rebase) Abort() 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
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 uint(C.git_rebase_operation_entrycount(rebase.ptr)) 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
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
err := C.git_rebase_abort(rebase.ptr)
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 {
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 MakeGitError(err)
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 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
} }
//Free frees the Rebase object and underlying git_rebase C pointer. //Free frees the Rebase object and underlying git_rebase C pointer.
@ -169,7 +184,5 @@ 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
int git_rebase_init_options(git_rebase_options *opts, unsigned int version); int git_rebase_init_options(git_rebase_options *opts, unsigned int version);
int git_rebase_open(git_rebase **out, git_repository *repo, const git_rebase_options *opts); int git_rebase_open(git_rebase **out, git_repository *repo, const git_rebase_options *opts);
git_rebase_operation * git_rebase_operation_byindex(git_rebase *rebase, size_t idx);
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
size_t git_rebase_operation_current(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: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

@ -29,12 +29,12 @@ func TestRebaseAbort(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.
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.
// TEST // TEST
repo := createTestRepo(t) repo := createTestRepo(t)
defer cleanupTestRepo(t, repo)
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.
seedTestRepo(t, repo) seedTestRepo(t, repo)
// Setup a repo with 2 branches and a different tree // Setup a repo with 2 branches and a different tree
err := setupRepoForRebase(repo, masterCommit, branchName) err := setupRepoForRebase(repo, masterCommit, branchName)
checkFatal(t, err) checkFatal(t, err)
defer cleanupTestRepo(t, repo)
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.
// Create several commits in emile // Create several commits in emile
for _, commit := range emileCommits { for _, commit := range emileCommits {
@ -84,12 +84,12 @@ func TestRebaseNoConflicts(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.
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.
// TEST // TEST
repo := createTestRepo(t) repo := createTestRepo(t)
defer cleanupTestRepo(t, repo)
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.
seedTestRepo(t, repo) seedTestRepo(t, repo)
// Setup a repo with 2 branches and a different tree // Setup a repo with 2 branches and a different tree
err := setupRepoForRebase(repo, masterCommit, branchName) err := setupRepoForRebase(repo, masterCommit, branchName)
checkFatal(t, err) checkFatal(t, err)
defer cleanupTestRepo(t, repo)
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.
// Create several commits in emile // Create several commits in emile
for _, commit := range emileCommits { for _, commit := range emileCommits {
@ -154,25 +154,41 @@ func performRebaseOnto(repo *Repository, branch string) (*Rebase, error) {
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.
} }
defer onto.Free() defer onto.Free()
// Init rebase
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.
rebase, err := repo.RebaseInit(nil, nil, onto, nil) rebase, err := repo.RebaseInit(nil, nil, onto, nil)
if err != nil { if err != nil {
return nil, err return nil, err
} }
opCount := int(rebase.OperationCount()) // Check no operation has been started yet
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 rebase.CurrentOperationIndex() != -1 { // -1 == GIT_REBASE_NO_OPERATION
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.
return nil, errors.New("No operation should have been started yet")
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.
// Iterate in rebase operations regarding operation count
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.
opCount := int(rebase.OperationCount())
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.
for op := 0; op < opCount; op++ { for op := 0; op < opCount; op++ {
operation, err := rebase.Next() operation, err := rebase.Next()
if err != nil { if err != nil {
return nil, err return nil, err
} }
// Check operation index is correct
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 rebase.CurrentOperationIndex() != op {
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.
return nil, errors.New("Bad operation index")
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 !operationsAreEqual(rebase.OperationAt(uint(op)), operation) {
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.
return nil, errors.New("Rebase operations should be equal")
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.
// Get current rebase operation created commit
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.
commit, err := repo.LookupCommit(operation.ID) commit, err := repo.LookupCommit(operation.ID)
if err != nil { if err != nil {
return nil, err return nil, err
} }
defer commit.Free() defer commit.Free()
// Apply commit
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.
err = rebase.Commit(operation.ID, signature(), signature(), commit.Message()) err = rebase.Commit(operation.ID, signature(), signature(), commit.Message())
if err != nil { if err != nil {
return nil, err return nil, err
@ -182,6 +198,10 @@ func performRebaseOnto(repo *Repository, branch string) (*Rebase, error) {
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.
return rebase, nil return rebase, nil
} }
func operationsAreEqual(l, r *RebaseOperation) bool {
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.
return l.Exec == r.Exec && l.Type == r.Type && l.ID.String() == r.ID.String()
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 createBranch(repo *Repository, branch string) error { func createBranch(repo *Repository, branch string) error {
commit, err := headCommit(repo) commit, err := headCommit(repo)
if err != nil { if err != 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.
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.