Skip to content

Cross-Repo-Issue-Pull #4

Description

@OttoRenner

Task:
Make Cross-Repo-Issue-Pulling work.
From: the FISI repo of /gordon-janicke
To: the current repos' project "KanBan".

How:
As a test, create a new issue in /Drogno/ainfluencer called "Cross-Repo-Issue-Pull-Test", also containing the description of the task.
Create a new entry in the KanBan board Backlog and select the "Cross-Repo-Issue-Pull-Test" Issue as its source.

Requirements:
(as far as I know, needs to be tested)
Each participant has a repo and has given Admin/Collab access to it to the other participant.

Status:
Admin access for /gordon-janicke in the KanBan Project established and tested on 24.08.2026. But he didn't receive an information about the change in status/admin invite via @. This may or may not be a problem/part of the problem.
He was not able to select one of his repos as a source.
I can not select him to assign an Issue. (Name not shown)

Problem:
/gordon-janicke has not given Admin access to a repo under /gordon-janicke

Solution:
/gordon-janicke hast to give Admin/Contributor access to one of hies repos

Test:
I have access to the repo /Drogno/ainfluencer and will try to post an Issue there and also give /Drogno Admin/Collab access to the current project/repo. Afterwards I will try to pull that issue into KanBan.

Must:
pull Issues reliably
Should:
pulled Issues can be moved and checked in the KanBan project by all participants
Could:
pulled Issues can be fully edited in the KanBan project by all participants
Won't:
all new issues are created in /Drogno/ainfluencer

DoD:

  1. The issue "Cross-Repo-Issue-Pull-Test" was pulled from /Drogno/ainfluencer into OttoRenner's FISIlabLE-Repo Project "KanBan".
  2. This new entry on the KanBan board can be moved/commented by all parties.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions