Added AUR PKGBUILD

[sandr01d]

Check list

• [ ] I have performed a self-review of my code
• [ ] I have commented my code in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation

Description

Adding the unchanged (and outdated) PKGBUILD of aur/forgit to the repository. I intentionally decided to add this without any changes, so all changes we make are transparent in the git history. This is the first step towards an automation for publishing new releases to the AUR. We could add the PKGBUILD of aur/forgit-git as well, but there wouldn't be anything to automate here, as this is a simple git package that installs from the latest commit of this repository. Does any of you have an opinion on that? I plan to send in another PR with changes as discussed in #311.

Type of change

• [ ] Bug fix
• [X] New feature
• [ ] Refactor
• [ ] Breaking change
• [ ] Documentation change

Test environment

• Shell
  • [X] bash
  • [X] zsh
  • [X] fish
• OS
  • [X] Linux
  • [ ] Mac OS X
  • [ ] Windows
  • [ ] Others:

[wfxr]

@sandr01d IMO it's better if we can avoid adding package manager-related files to the main repository. The usual practice is to directly update the files on aur in ci workflow, or create an independent repo to be responsible for publishing the latest version to the corresponding warehouse.

[sandr01d]

Alright, I'll update the files inside the CI workflow then.