Closed rahulsuresh-git closed 4 months ago
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (
1afeeb0
) 6.42% compared to head (18e5802
) 6.42%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@toninis Any ideas why we need to press "Approve and run" on each commit of this forked repo PR?
Workflows for this repo are here https://github.com/mattermost/mattermost-plugin-todo/tree/master/.github/workflows. Not sure which ones are the "2 workflows awaiting approval"
@toninis Any ideas why we need to press "Approve and run" on each commit of this forked repo PR?
Workflows for this repo are here https://github.com/mattermost/mattermost-plugin-todo/tree/master/.github/workflows. Not sure which ones are the "2 workflows awaiting approval"
This is the organisation default behaviour on forked PRs for security reasons @mickmister
@toninis Is this rule enforcement new? I know there is a "first-time contributor" check that has been enabled for a while, though I'm not used to seeing this for every commit
@toninis Is this rule enforcement new? I know there is a "first-time contributor" check that has been enabled for a while, though I'm not used to seeing this for every commit
https://github.com/mattermost/mattermost/pull/25616 It's always like this if I recall
Removing myself from the list of reviewers until the comments of @mickmister are resolved.
Closing this PR as the changes are moved to this single PR: https://github.com/mattermost-community/mattermost-plugin-todo/pull/254. Note: Comments addressed on the single PR.
Summary
This introduces a Playwright end-to-end (e2e) test to check if the
/todo help
command functions as expected. We verify the functionality of the various commands available for the Todo plugin.I've also made a few changes to improve clarity and readability. Verified that the test passes locally.