Decide what to do with the Git abstraction and deprecated it from the backend-common package

[camilaibs]

Context

Ref: #24493

Before the stable release, we will be deprecating the backend common package, and the Git abstraction will be moved elsewhere. This task is for us to decide what to do with the Git abstraction, and then make the changes according to our decision.

Open questions

Some of it can be moved into scaffolder-node implementations, but more discussion is needed.

Suggested approach

• Determine whether more than one plugin uses it
• Examine whether it fits with a new backend concept
• Extract the files and update the references import statements
• Deprecate the export from the backend common package (re-export from the new package with "@deprecated" as a annotation)
• Verify everything is working as before and update any documentation

[javiermartingonzalez]

Hello, how can I use the Git abstraction after deprecation?

[camilaibs]

Hi @javiermartingonzalez 👋🏻 , as we mentioned in the changelog, the abstraction will be removed from the backstage backend packages because it is not used in the framework itself, the implementation was created by the community and was only used by plugins. We recommend you copying the implementation to you plugin in case you are using it or as it’s a fairly thin wrapper on top of the underlying library you may enjoy using that directly instead of the wrapper 🙂 .