Souryavardhan singh
Souryavardhan singh
okay @princerajpoot20 the issue was in if-nodejs-pr-testing.yml where -> .number on a null object cauing error (github.event.pull_request.number != '' )
@sammy200-ui both approaches seem feasible. Looping in @princerajpoot20 to review.
@princerajpoot20 The workflow PR testing - if Node project was manually disabled -> (you can see the yellow banner in the Actions tab). That's why all PRs are stuck -...
@princerajpoot20 the ci pipeline is working fine now.
@princerajpoot20 this was disabled before that why ->CI pipeline is failing for now it have been enabled ->check it in action tab
am i missing something here ?
Actually from my point of view I thought that it can be issue that’s why I mentioned that . Thanks for your time ☺️
@princerajpoot20 the ci issues have been fixed ?
[FEATURE] Strengthen frontend test coverage with component tests, a11y checks, and visual regression
@princerajpoot20 just review this issue in your free time 😊.
[FEATURE] Strengthen frontend test coverage with component tests, a11y checks, and visual regression
@derberg take a look on this most of the components are not in test coverage we can add this to prevent future bugs Thank you ☺️