Responses that are submitted in this format through CATcher will be rejected

[JunWei96]

For example, submit the following string as a team's response through CATcher. The response will not be registered as being responded in CATcher. This bug will probably also be present in other phases that uses regex.

# Team's Response
No response provided.

 ## Duplicate status (if any):
--

[damithc]

There is no reason for this to happen 'accidentally' if a user is using CATcher right?
What if we allow a user to use the GitHub interface because she can't use CATcher for some reason? Would this issue cause a problem then?

[JunWei96]

There is still a possibility. In fact, if the user submits in the following format through CATcher, CATcher will mark the issue as not responded too.

# Team's Response
test

If we allow a user to use Github interface then I suppose the user would need to submit their responses in the required format?

[damithc]

There is still a possibility. In fact, if the user submits in the following format through CATcher, CATcher will mark the issue as not responded too.

# Team's Response
test

But the user has no reason to type # Team's response right? Perhaps we should make the internal format such that it is not something a user will type 'accidentally.

e.g., # [[Team's Response]]

If we allow a user to use Github interface then I suppose the user would need to submit their responses in the required format?

Yes.

[JunWei96]

I have made a PR to fix this. It is a simple fix that relaxes the rule on what is considered the "correct" format. So I don't think we need to change the internal format.