XS ◾ Change from BCC to CC "followupthen"

[tiagov8]

cc @mishmanners @christianmorfordwaitessw

1. What triggered this change? (PBI link, Email Subject, conversation + reason, etc)

@adamcogan 's email: Re: Rule - Change indentation and add >

2. What was changed?

from BCC to CC as the standard

[github-actions]

PR Metrics

✔ Thanks for keeping your pull request small.

	Lines
Product Code	13
Test Code	-
Subtotal	13
Ignored Code	-
Total	13

Metrics computed by PR Metrics. Add it to your Azure DevOps and GitHub PRs!

[github-actions]

Hi @tiagov8,

We found some markdown suggestions for your Pull Request:

File	Error	Rule
rules/follow-up-effectively/rule.md	Line 79: column count	Rule MD056
rules/follow-up-effectively/rule.md	Line 134: list item prefix	Rule MD029
rules/follow-up-effectively/rule.md	Line 140: list item prefix	Rule MD029
rules/follow-up-effectively/rule.md	Line 141: list item prefix	Rule MD029
rules/follow-up-effectively/rule.md	Line 145: list item prefix	Rule MD029
rules/follow-up-effectively/rule.md	Line 146: list item prefix	Rule MD029

Please review and update your Markdown files accordingly.

[uly1]

i disagree. if you cc it, both you AND the client will be sent the follow up. I only want myself to be prompted so then I can follow up the client/dev/whatever myself.
I almost never CC FUT for that reason. i sent it to the to for a future task to mnyself, or the BCC for a reminder to follow up someone else

[tiagov8]

i disagree. if you cc it, both you AND the client will be sent the follow up. I only want myself to be prompted so then I can follow up the client/dev/whatever myself. I almost never CC FUT for that reason. i sent it to the to for a future task to mnyself, or the BCC for a reminder to follow up someone else

Hi @uly1

Agree, I have altered my PR changes to reflect that.
Please review again

[github-actions]

Hi @tiagov8,

We found some markdown suggestions for your Pull Request:

File	Error	Rule
rules/follow-up-effectively/rule.md	Line 79: column count	Rule MD056
rules/follow-up-effectively/rule.md	Line 134: list item prefix	Rule MD029
rules/follow-up-effectively/rule.md	Line 140: list item prefix	Rule MD029
rules/follow-up-effectively/rule.md	Line 141: list item prefix	Rule MD029
rules/follow-up-effectively/rule.md	Line 145: list item prefix	Rule MD029
rules/follow-up-effectively/rule.md	Line 146: list item prefix	Rule MD029

Please review and update your Markdown files accordingly.

[github-actions]

Howzit @tiagov8,

This PR has been here a while.

Did you know you should avoid merge debt?

1. Please action (e.g. get a review) and merge or close

Thanks!