q02/pool.v0.trr379.de-ui
9
0
Fork 1
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

config for file uploads #14

Closed
a.wagner wants to merge 1 commit from a.wagner/pool.v0.trr379.de-ui:file-upload into main
pull from: a.wagner/pool.v0.trr379.de-ui:file-upload
merge into: q02:main
Conversation 3 Commits 1 Files changed 1 +5
a.wagner commented 2026-01-30 13:10:54 +00:00
Member
Copy link

The TRR Knowledge Pool does not yet have file upload enabled. This PR sends a skeleton config, which still needs the UUID of the repository to which files shall be uploaded.

The TRR Knowledge Pool does not yet have file upload enabled. This PR sends a skeleton config, which still needs the UUID of the repository to which files shall be uploaded.
jsheunis commented 2026-01-30 13:23:21 +00:00
Member
Copy link

Nice.

Perhaps it's already useful to also add a repo_url field here, since we wouldn't know/remember the file upload repo URL otherwise. An extra sub-property in the shacl-vue config shouldn't break anything AFAIR.

Unless there are reasons not to make that url public?

Nice. Perhaps it's already useful to also add a `repo_url` field here, since we wouldn't know/remember the file upload repo URL otherwise. An extra sub-property in the shacl-vue config shouldn't break anything AFAIR. Unless there are reasons not to make that url public?
a.wagner changed title from WIP: skeleton config for file uploads to config for file uploads 2026-01-30 13:37:43 +00:00
a.wagner commented 2026-01-30 13:39:28 +00:00
Author
Member
Copy link

Perhaps it's already useful to also add a repo_url field here, since we wouldn't know/remember the file upload repo URL otherwise. An extra sub-property in the shacl-vue config shouldn't break anything AFAIR.

I'm still not done understanding what is needed for the file upload CI, but per my current understanding this would be necessary, yes. I do not know how I would be able to derive the target repo only from the UUID.

However, I wonder if there was a reason to keep the target repo private? If so, can you share that?

> Perhaps it's already useful to also add a repo_url field here, since we wouldn't know/remember the file upload repo URL otherwise. An extra sub-property in the shacl-vue config shouldn't break anything AFAIR. I'm still not done understanding what is needed for the file upload CI, but per my current understanding this would be necessary, yes. I do not know how I would be able to derive the target repo only from the UUID. However, I wonder if there was a reason to keep the target repo private? If so, can you share that?
mih commented 2026-03-31 06:17:34 +00:00
Owner
Copy link

This is now part of the live config. Thanks!

This is now part of the live config. Thanks!
mih closed this pull request 2026-03-31 06:17:34 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
q02/pool.v0.trr379.de-ui!14
No description provided.