I'm now not so sure whether I want the headache of this as the needs it was intended to serve are actually already mostly met in other ways.
I mirror my Github repos into Gitlab, so issues get updated for Github commits which mention them (could also have been done via webhook, but it allows the commit to be viewed in GL/GILS).
I've got a wrapper around the Github CLI which mirrors issues from my repo down into text files:
cd $BASEDIR
for repo in $REPOS
do
mkdir -p $repo
cd $repo
for id in `gh issue list -R $repo -L 3000 --state all | awk '{print $1}'`
do
gh issue view -c -R $repo $id | tee issue_$id.txt.md
done
cd $BASEDIR
done
Where BASEDIR is the directory to write into, and REPOS is a space seperated list of repos pulled from the GH API.
That allows my search engine to index my GH issues, which was the only real reason for wanting to include them.
I'm open to reconsidering later, but for now, I'll close as Won't Fix
Activity
15-Oct-21 10:05
assigned to @btasker
21-Apr-22 19:14
I'm now not so sure whether I want the headache of this as the needs it was intended to serve are actually already mostly met in other ways.
I mirror my Github repos into Gitlab, so issues get updated for Github commits which mention them (could also have been done via webhook, but it allows the commit to be viewed in GL/GILS).
I've got a wrapper around the Github CLI which mirrors issues from my repo down into text files:
Where
BASEDIR
is the directory to write into, andREPOS
is a space seperated list of repos pulled from the GH API.That allows my search engine to index my GH issues, which was the only real reason for wanting to include them.
I'm open to reconsidering later, but for now, I'll close as Won't Fix