Link Bazel badge in the Bazel README section to the actual CI test

[Sanket-0510]

The link to the bazel build is broken or rather it is not provided, I have added the right link for the same.

[fruffy]

That's a funny one, thanks for spotting it. Can you please make the pull request title more precise? Describe more clearly what broken link is fixed here.

Then we can merge this one.

[Sanket-0510]

That's a funny one, thanks for spotting it. Can you please make the pull request title more precise? Describe more clearly what broken link is fixed here.

Then we can merge this one.

Hey @fruffy the given image is supposed to be link for the bazel build
like these one -
https://github.com/p4lang/p4c/blob/0685e1a00c899a54d719ff67cd4b5f0a551e8778/README.md?plain=1#L1C1-L5C1

I know this is silly but I just spotted it and thought it can be fixed, pardon me if that is not the expected behaviour for the same

[fruffy]

Thanks! On naming your pull requests and commits I would recommend following conventions such as the imperative style. I edited the title with an example of how to do this.

There are some guides out there, for example:
https://cbea.ms/git-commit/
https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html

These guidelines are not mandatory, for example I prefer to use periods, but are good to keep in mind.

[Sanket-0510]

Thanks! On naming your pull requests and commits I would recommend following conventions such as the imperative style. I edited the title with an example of how to do this.

There are some guides out there, for example: https://cbea.ms/git-commit/ https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html

These guidelines are not mandatory, for example I prefer to use periods, but are good to keep in mind.

thanks for this @fruffy I will make sure to follow these from next time