mattermost / mattermost/mattermost-plugin-gitlab
Webhooks don't always resolve username
Open
Nobody has claimed this yet.
Help Wanted
Tech/Go
Type/Enhancement
Up For Grabs
- Dominant language
- JavaScript
- Stars
- 152
- Forks
- 97
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 8
Description
Creating tags and issues yields the following:
It seems as if
https://github.com/mattermost/mattermost-plugin-gitlab/blob/442334dbe0ec95127d7d7f50330aaea3adbbe71a/server/webhook/tag.go#L43
goes awry. couldn't it just use UserName directly?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read server/webhook/tag.go around line 43 and inspect how the username is resolved for tag and issue creation webhooks. Reproduce the reported behavior with those webhook events, then verify that the generated Mattermost content consistently shows the username.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100