Using Gitea Issues to manage Google Docs

We are considering using Gitea Issues to keep track of Google Docs.

Each Google Doc has a URL. For example,

https://docs.google.com/document/d/1YKb-yvFPOb_EWD-Nu92mjy3L8CKv1-s8gEuGJsCHG4M/

is the URL of a Google Doc.

Let’s say I were to create one thousand untitled Google Docs, place their 1000 URLs into a text file, and then upload that file to a directory in Gitea.

As a result, each time a user creates a new issue in Gitea, I would want that issue to be populated with the next URL in the text file.

For example, if a user named Ben were to create Issue 1, then Issue 1 would be populated with the first URL in the text file. Subsequently, if a user named Joe were to create Issue 2, then Issue 2 would be populated with the second URL in the text file. And so on.

Essentially our problem is this: we want to use a simple task management system that allows us to use Google Docs as our editor because Google Docs has numerous features we like.

However, Google Workspace doesn’t provide a native method for doing things like prioritizing Google Docs, setting due dates for Google Docs, or marking a Google Doc as closed.

I have toyed with Google Apps Scripts, but, at the end of the day, it I failed to make it do what we want.

I could see how todo it via either gitea actions or a simple webhook bot.
You essentially trigger it on the “new issue” event. The trick then is to access this list (git repo) to determine the “next” url to enter as the reply.

The issue will be stateful vs stateless to determine what the next entry should be…

How about having two files “Not_yet_assigned.txt” and “Currently_assigned.txt”?

The 1000 URLS would all be initially listed in “Not_yet_assigned.txt”. When a URL was populated into a new issue, that URL would be moved to “Currently_assigned.txt.”