feat: default hashtag includes channel name

[will7200]

Summary

Closes #10
Default hashtag to use the first 15 characters of a channel name prefixed to the date format.

Ticket Link

JIRA: https://mattermost.atlassian.net/browse/MM-22727

[jfrerich]

LGTM. Would you mind adding an update to the README letting users know what the default will be?

[attilamolnar]

The approach taken in this PR leads to incorrect results, explaination and examples in #10 (comment).

[iomodo]

Thanks for the contribution @will7200 !
Small change request bellow

[jfrerich]

Thanks @will7200!

[marianunez]

Thanks @will7200! Apologies on the delay on this review. Everything looks good, great tests!

Just wanted to include a request to add the new requirement for date format
to the help text in the settings modal here

Maybe adding:

Embed a date writing down what January 2, 2006 would look like within double curly braces, i.e. {{Jan02}}

[codecov]

Codecov Report

Merging #30 into master will increase coverage by 11.81%.
The diff coverage is 88.23%.

@@             Coverage Diff             @@
##           master      #30       +/-   ##
===========================================
+ Coverage   16.46%   28.27%   +11.81%     
===========================================
  Files           6        6               
  Lines         328      343       +15     
===========================================
+ Hits           54       97       +43     
+ Misses        262      229       -33     
- Partials       12       17        +5     

Impacted Files	Coverage Δ
server/meeting.go	65.30% <88.23%> (+41.77%)	⬆️
server/utils.go	95.12% <0.00%> (+46.34%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 853bfe1...2302c21. Read the comment docs.

[will7200]

@marianunez I was finally able to get around this, thank you for your patience. I added as instructed.

[hanzei]

@will7200 Heads up that I merged master into your branch to update it which has broken CI. Could you please take a look?

[will7200]

@hanzei Fixed

[marianunez]

Thanks @will7200. LGTM after @jfrerich suggestions and resolving the merge conflicts below.

[hanzei]

@will7200 Could you please resolve the merge conflicts?

[will7200]

@hanzei done

[hanzei]

Thanks @will7200 👍

[hanzei]

@jfrerich Could you give this PR a final review?

[jfrerich]

LGTM! Thanks again, @will7200!

[hanzei]

@marianunez @DHaussermann Should this PR get QA reviewed or can we merge it as it is?

[marianunez]

Should this PR get QA reviewed or can we merge it as it is?

If we do skip the QA review here, I would suggest a quick smoke test to the release before deploying to community.

Conversation resolved