Closes #196 Check post tags using CICD

[manciniedoardo]

Thank you for your Pull Request! We have developed this task checklist to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your blog post.

Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the main branch until you have checked off each task.

• [x] Place Closes # into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update), and make sure the corresponding issue is linked in the Development section on the right hand side
• [x] Run the script from CICD.R line by line to first check the spelling in your post and then to make sure your code is compatible with our code-style. Address any incongruences by following the instructions in the file!
• [x] Choose (possibly several) tag(s) or categories from the current list: c("Metadata", "SDTM", "ADaM", "TLG", "Shiny", "Community", "Conferences", "Submissions", "Technical") for your blog post. If you cannot find anything that fits your blog post, add your own tag! We occasionally tidy up all tags for consistency.
• [x] Add a short description for your blog post in the description field at the top of the markdown document.
• [x] Blog post is short, personalized, reproducible and readable
• [x] Add a disclaimer at the top of your post, if appropriate (example: Disclaimer This blog contains opinions that are of the authors alone and do not necessarily reflect the strategy of their respective organizations.)
• [x] Address all merge conflicts and resolve appropriately
• [x] Assign two of us (@bms63, @manciniedoardo, @StefanThoma, @kaz462) as reviewers in the PR.
• [x] Pat yourself on the back for a job well done! Much love to your accomplishment!

[manciniedoardo]

@bms63 @StefanThoma @gigikenneth

I've got something super basic working in this PR. Infact the check flags an issue that we had not noticed (posts tagged as "Submissions" vs "Submission"). I think it can be enhanced and improved before merging in. Some ideas:

• Where should the list of allowable tags be stored? Currently this is just within the check function but this then duplicates the info in the pull request template.
• Check function should ideally print out:
  • List of posts where tags are mismatching (not just the first post).
  • Which tags are mismatching
  • Suggest how to fix or add a new tag.

What do you think?

[bms63]

Dang...this is awesome! Can it say which tag is culprit?

[manciniedoardo]

@StefanThoma @bms63 @gigikenneth

I gave it another pass following your review - let me know your thoughts now. I created an allowed list of tags script and stored them in there, but I'm wondering now whether that is even a good idea as we mention the allowed list of tags:

• In the README
• In the PR template
• In the CICD action
• In the create_blog_post script and we can only really use the allowed list of tags in the final two places. So is it worth it?

Also the CICD error message throws a weird code, not sure what that's about:

Once we are happy with this PR, i can retroactively change the tags on the "Submission" posts and then merge in.

[bms63]

Now you just have to first the failing CI :)