[Question]: Connection between Awork and Github

[dnehl]

What is your question?

Hi,
We would like to integrate Awork with Github as is the case in other tools (e.g. Jira).
Do you work internally with Github and Awork? How did you implement this - do you have a case study for this?

Do you have a trace id of the call?

No response

[sebastianrosch]

Hi @dnehl,

we use Github internally and have built some serverless functions to update tasks based on linked Pull Request status. We use awork to track issues as tasks in a dedicated project. When we close a PR that has a task linked, we update the task to a QA status so it can be verified in the respective environment.

I hope this helps. Let me know if you have any more questions.

[dnehl]

thanks for the quick response!
It would be nice if we have - someday - a possibility to create branches directly from awork and link prs directly.. :)

But this means, you have to add the awork task id manually in the pr or name the pr/branch like the item, so that your function can update the task?

[sebastianrosch]

A good way to achieve something like this could be a Chrome plugin that knows the page you're on and can do this action for you given the context, so for example create a branch and link to the awork task.

[timkley]

@sebastianrosch I just stumbled upon this issue and your comment made me curious. We've been toying with the idea to develop a Chrome plugin to tie together other internal tools of ours with awork.

Are there any recommendations how to inject HTML into your DOM that is future proof?
Besides the URL, are there other ways to know the current entity, like a global window state?

Thanks up front!

[nilzzzzzz]

@santiagof4 can you help out here, afaik besides the url there is no stable way.

[santiagof4]

@timkley We do not expose any global window state, so for now the URL is the only way to know the current entity.