GIT Repository Management

[jon-nfc]

---

Addendum 2024-08-20

repositories should be added as a project. Re-plan this feature.......

a git repo should be an item under devops which will enable the management of the repo. A git repository that is not part of devops will not import any item/object from github/gitlab. Only items that are specifically added. i.e. an issue or MR.

Once added to devops a project should be created that then within the tasks has the issues and merge requests as tasks and if assigned to a milestone a sub of that.

---

add git repository management features

Details

each repository be placed within a group (organization on github). this will then be used to build repository url for the relevant provider.

groups will be able to hold settings as well as repositories. If the provider is Github, the nested groups will no be allowed.

• No nested groups for Github (Validator) #249

• Models

  • Groups

    • id

    • parent

    • provider (Github/Gitlab)

    • methods

      • url. get group URL

  • Repository

    • id

    • group

    • path

    • name

    • description

    • tags

    • provider (Github / Github)

    • private. is repo public

    • credentials Foreign Key pk of api credential.

    • Methods

      • url. build complete repo url.

Features

• Related ticket slash commands #287 slash command /<action> https://github.com/nofusscomputing/centurion_erp/issues/250 will add the github issue as related

• add/change/delete/view repo

• config renders for role git_configuration as part of config management

Requirements

• Uses ansible role git_configuration

• Tracks sync status

  will need to track sync status so as to know when and if synced.

• GitHub/Gitlab Related Item

  if a user uses a slash command /related https://github.com/nofusscomputing/centurion_erp/issues/250 the item is added to a ticket as related. Once the item is related, there will need to be a job that checks the related items status.

• Inbound Web hooks

  • Inbound webhooks from Github
  • Inbound webhooks from Gitlab
  • Inline form editing for tickets
    assign ticket, project, roadmap, priority, urgency, impact. Inline comments. inline edit comment. inline related comment.

Addition Features new issue??

• ~Feature Sync issues

• ~Feature sync MR

• ~Feature sync milestones

• ~Feature Scrum Board

  • Labels
  • Links to Gihub/Gitlab labels
  • links to Github/gitlab milestones

• ~Feature Issue/MR as project Management task

• A Comment on a GIT ticket updates the relevant item (issue/MR/PR) on gitlab/github.

  Uses current authenticated users Github/Gitlab API Key. Storing of API Credentials #138

Links

• Blocks: Request Management Module #96

• Blocked By: Gitlab API Browser #128

• Blocked By: Github API Browser #129

• Blocked By: Ticketing models #250

• Related: Project Management #14

• Related: Config management module #33

• Related: devops module #68

• Related: AWX Integration #113

• Related: Storing of API Credentials #138

• Related: Assign KB article to an item #149

• Related: Git Repository Reporting (Prometheus) #158

• Related: import repository from gitlab #167

• Related: import repository from github #168

• Releated: Related ticket slash commands #287

[jon-nfc]

marked this issue as related to #33

[jon-nfc]

marked this issue as related to #113

[jon-nfc]

added 3m of time spent

[jon-nfc]

marked this issue as related to #68

[jon-nfc]

marked this issue as blocked by #128

[jon-nfc]

marked this issue as blocked by #129

[jon-nfc]

marked this issue as blocking #96

[jon-nfc]

marked this issue as related to #138

[jon-nfc]

added 15m of time spent

[jon-nfc]

marked this issue as related to #14

[jon-nfc]

marked this issue as related to #149

[jon-nfc]

marked this issue as related to #158

[jon-nfc]

marked this issue as related to #167

[jon-nfc]

marked this issue as related to #168