Commits on Nov 16, 2022

1. Allow unsupported multi_ack capability …

   Azure DevOps requires capabilities multi_ack / multi_ack_detailed,
   which are not fully implemented and by default are included in
   transport.UnsupportedCapabilities.
   
   The initial clone operations require a full download of the repository,
   and therefore those unsupported capabilities are not as crucial, so
   by removing them from that list allows for the first clone to work
   successfully.
   
   Additional fetches will yield issues, therefore to support that
   repository users have to work from a clean clone until those
   capabilities are fully supported. Commits and pushes back into the
   repository have also been tested and work fine.
   
   This change adds an example for cloning Azure DevOps repositories.
   
   Signed-off-by: Paulo Gomes <pjbgf@linux.com>

   

   pjbgf committed Nov 16, 2022
   Copy the full SHA

   9c7d2df View commit details

   Browse the repository at this point in the history