Stuck at wekan-ldap: updating npm dependencies -- ldapjs...

Migration did clone repo, but did not clone issues

ohh issues I dont think that works yet let me check

I will try to mirror the wekan repo

Mirroring wekan repos did work

Here is some other issue mirroring code https://github.com/MichaelMure/git-bug but I don't know is there something for Gitea

Sometimes GitHub is down, so I would like to mirror all to Gitea

Sometimes GitHub is down does that happen :-O

I did mirror wekan repo by adding my Wekan GitHub API key to Gitea migration username field. I have not tried does migration work without API key.

i just mirrored my wekan fork and it seems to be have done it

issues are not there obviously though

https://hn.algolia.com/?dateRange=pastMonth&page=0&prefix=false&query=github%20down&sort=byPopularity&type=story

GitHub is down quite often

oh I didnt noticed that much, probably coz I dont use it much as well

I think it does not make sense to fetch all not all the time but when needed

here is what we are planning on doing for starters

add custom field in board called gitea-issue

anytime a card is created in open list / bug label is added to any card I would like to create a gitea issue for it

once the gitea issue is created will be assigning the gitea issue number to the custom field

also there will be a board for every gitea repo so in order to keep them in sync we will be relying on the naming of the repo and board

so say if i have a repo dineshsalunke/sample-repo then there will be a board called dineshsalunke/sample-repo

setting up such conventions for now, till we find better ways to handle integration

so now in order to do this we would like to fetch some card, list and board info

the current way to do this is using the ids from the webhook, first get the card then get the board then get the list

I think this could be made simple

and if it does than using node-red sort of thing to do your workflows would be a lot easier