When I log into Gitlab through gitlab.eclipse.org, I am logged in as @agarciad1 and not as @agarciad. This means that I cannot add my usual SSH key to my account, so I cannot push. When I try to push, I get this:
remote: remote: ========================================================================remote: remote: You are not allowed to push code to this project.remote: remote: ========================================================================remote: fatal: Could not read from remote repository.
Edited
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related or that one is blocking others.
Learn more.
Activity
Sort or filter
Newest first
Oldest first
Show all activity
Show comments only
Show history only
Antonio Garcia-Dominguezchanged title from Cannot push to migrated Hawk project to Cannot push to migrated Hawk project (wrong login)
changed title from Cannot push to migrated Hawk project to Cannot push to migrated Hawk project (wrong login)
Additionally, every time I log in I have to go through the same "Do you want to authorize this application to use your account?" page. Shouldn't it be enough to authorize it once?
If possible and it doesn't include any sensitive information, can you include the full commit message? I have a possible fix and synthetic test case, but having a real-world use case is always best if possible! I want to be sure I address the issue you're hitting, not just the 90% case
I was able to push now (thank you!), but I'm seeing these messages now:
remote: Commit: 41accf96f7b54f3b96bc0f36c30734aa172f622e ✔remote: remote: Reviewing commit: 41accf96f7b54f3b96bc0f36c30734aa172f622eremote: Authored by: Antonio García-Domínguez <agarcdomi@gmail.com>remote: The author is a committer on the project.remote: Reviewing commit: 41accf96f7b54f3b96bc0f36c30734aa172f622eremote: Authored by: Antonio García-Domínguez <agarcdomi@gmail.com>remote: The author is a committer on the project.remote: Any warnings noted above may indicate compliance issues with committer ECA requirements. More information may be found on https://www.eclipse.org/legal/ECA.phpremote: remote: remote: Commit: 32975427e48f84f20084aedc8ae207542f906e79 ✔remote: remote: Reviewing commit: 32975427e48f84f20084aedc8ae207542f906e79remote: Authored by: Antonio García-Domínguez <agarcdomi@gmail.com>remote: The author is a committer on the project.remote: Reviewing commit: 32975427e48f84f20084aedc8ae207542f906e79remote: Authored by: Antonio García-Domínguez <agarcdomi@gmail.com>remote: The author is a committer on the project.remote: Any warnings noted above may indicate compliance issues with committer ECA requirements. More information may be found on https://www.eclipse.org/legal/ECA.phpremote: remote: remote: Commit: f1bc5d90755b138a457cf1c579a8b683b33c0314 ✔remote: remote: Reviewing commit: f1bc5d90755b138a457cf1c579a8b683b33c0314remote: Authored by: Antonio García-Domínguez <agarcdomi@gmail.com>remote: The author is a committer on the project.remote: Reviewing commit: f1bc5d90755b138a457cf1c579a8b683b33c0314remote: Authored by: Antonio García-Domínguez <agarcdomi@gmail.com>remote: The author is a committer on the project.remote: Any warnings noted above may indicate compliance issues with committer ECA requirements. More information may be found on https://www.eclipse.org/legal/ECA.phpremote: remote:
Do we really need these messages if the commits are fine? I don't really mind them, but they seem somewhat redundant. By the way, for some reason each commit is reviewed twice.