Add 'gitea_api' module and 'git-obs' executable

[dmach]

TODO

• print a proper error message when there's no default config entry
• login list
• login add
  • create directories, set secure perms
  • Implement --set-as-default
• login remove
• login update
  • Implement --set-as-default
• ssh-key list
• ssh-key add
  • validate that we're sending a public ssh key
• ssh-key remove
• clone
  • replace --directory option with an optional argument to get closer to the git clone command?
  • move under repo command
• fork
  • move under repo command
• make available as git obs subcommand

[pep8speaks]

Hello @dmach! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

• In the file osc/commandline_common.py:

Line 226:121: E501 line too long (134 > 120 characters)
Line 240:121: E501 line too long (149 > 120 characters)

• In the file osc/commandline_git.py:

Line 73:121: E501 line too long (130 > 120 characters)
Line 90:5: E303 too many blank lines (2)

• In the file osc/commands_git/login_add.py:

Line 31:121: E501 line too long (146 > 120 characters)

• In the file osc/commands_git/repo_fork.py:

Line 36:121: E501 line too long (143 > 120 characters)

• In the file osc/gitea_api/branch.py:

Line 72:121: E501 line too long (136 > 120 characters)

• In the file osc/gitea_api/connection.py:

Line 38:121: E501 line too long (137 > 120 characters)
Line 56:121: E501 line too long (140 > 120 characters)

• In the file osc/gitea_api/fork.py:

Line 47:121: E501 line too long (134 > 120 characters)

Comment last updated at 2024-10-11 11:13:56 UTC

[dmach]

@dcermak could you review the code and check if it works for you?

[DimStar77]

Is this mostly a re-implementation of gitea-tea to interact with a gitea instance?

[dmach]

Is this mostly a re-implementation of gitea-tea to interact with a gitea instance?

The basic functionality is going to be similar.
I'm planning to add interactive reviews similar to what osc has already
and some goodies to support the packaging workflows.
Those still need to be clarified.

IIUC @AdamMajer is working on a staging tooling that overlaps with this tool. We'll need to decide if we need both.

[AdamMajer]

Interactive reviews should use "Issue comments" and "Pull Request Reviews" API to read and leave comments on a PR.

My ideal state is to use GPG signatures for approvals and not rely on Gitea as a secure record of this data. But we'll still need a tool to do actual review (ie. diffs) and communication.

[dirkmueller]

as discussed in the sync meeting, the extra binary should be called "git-obs" to have it callable via "git obs"