Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detect issues from commit messages #4

Closed
vajahath opened this issue Jul 11, 2017 · 1 comment
Closed

Detect issues from commit messages #4

vajahath opened this issue Jul 11, 2017 · 1 comment
Assignees

Comments

@vajahath
Copy link
Owner

Opening discussion on Issue tracking

Give feedbacks here

requirement

We need the following things to create a new activity:

  • Project ID βœ… done
  • Issue ID πŸ‘ˆ current focus 🎯
  • Start time ⚠️ pending
  • End time ⚠️ pending
  • Message βœ… done

Currently auto-timesheet fetches git-commit-messages from Github and use it as the message for timesheet activity. We need to somehow extract the issue id from commit messages.

Proposal

Just a proposal to start thinking..

Lets use ti#tags with commit messages. While making a commit message, mention the timesheet issue with a hashtag like:

Adds extra details to fetch details api. ti#fetchDetails

(where fetchDetails is the timesheet issue corresponding to our commit)

We can extract that ti# tag and find that issue-id.

How to detect issue-id from extracted tags?

Looks like timesheet uses an api to fetch all issues (description and id) corresponding to a project. We call that api and get those data. Now we've to match our hashtag with the issue description to get the id.

Why ti# ?

Github uses hashtags to map stuffs made in Github itself (PR/issues). Prepending ti (stands for Timesheet Issue) with it resolve that conflict.

How to handling multiple ti# tags in a message ?

If a timesheet msg contains multiple ti# tags, let's choose one in random..

@vajahath vajahath self-assigned this Jul 11, 2017
vajahath added a commit that referenced this issue Jul 12, 2017
@vajahath
Copy link
Owner Author

resolved by #6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant