Add elements from repositories under different org / owner #74
Comments
|
It's definitely on the radar to support across the board. I don't have a timeline for this yet |
At present, this Action only supports adding an issue or pull request to a project in the *same organization* as the issue or pull request itself. This removes that limitation. If the issue/pull request and project have different owners, then instead of directly creating a project item, we will instead create a "draft issue" which will be added to the board. Fixes actions#74.
At present, this Action only supports adding an issue or pull request to a project in the *same organization* as the issue or pull request itself. This removes that limitation. If the issue/pull request and project have different owners, then instead of directly creating a project item, we will instead create a "draft issue" which will be added to the board. Fixes actions#74.
At present, this Action only supports adding an issue or pull request to a project in the *same organization* as the issue or pull request itself. This removes that limitation. If the issue/pull request and project have different owners, then instead of directly creating a project item, we will instead create a "draft issue" which will be added to the board. Fixes actions#74.
At present, this Action only supports adding an issue or pull request to a project in the *same organization* as the issue or pull request itself. This removes that limitation. If the issue/pull request and project have different owners, then instead of directly creating a project item, we will instead create a "draft issue" which will be added to the board. Fixes actions#74.
|
Awesome!!! |
|
Unfortunately I can't get it to work:
Was it closed in error? |
|
@aeneasr can you try v0.3.0? I believe that's when this capability was released. |
|
Yes, perfect, thank you! One problem remains though - this doesn't work when people push from forks as the token is not available on the fork due to security settings. Is there a way to work around this (preferrably not making the token available to forks :D )? |
No problem!
I'm going to leave this one for @mattcosta7 |
@aeneasr would you mind writing that up in a bit more detail on a new issue so we can look into what/if any updates we can make here to support it? |
|
I just tried this out and received a "Creating draft issue in project" message. However, I don't see any (draft) issues in the project. Am I missing something? For additional context, this project is currently private but I didn't think that would matter as long as the token has access.
|
It uses a quirk of the API to make a draft - which is immediately converted to a real issue since it's added by URL (which is the same way projects work when copying/pasting a link to an issue/pr into a project) |
|
Hmm... but I'm still not seeing the issue show up in my project. I turned on debugging but there wasn't anything useful. Anything that I can try to dig into this? |
|
I can confirm that the issues are correctly added to the board for me, even though the repository is in org A and the project board in org B |
As noted in the README
and also raised on the feedback forums (without ack from GH) it is not possible to add issues to a board that belongs to a different org. As this is possible in the UI, it appears to be a validation issue in the GraphQL API.
My question / suggestion is, will this ever become possible? It would be a huge relief in managing multi-org set ups that popular open source ecosystems use, such as Ory.
Thanks! :)
The text was updated successfully, but these errors were encountered: