Kindly check this and merge before 31

Kindly check this and merge before 31

Hey @Ritesh-Udgata, thanks for picking this up and working on it—great job!

A few points (only 1 and 2 require changes from you):

1. It appears the DCO check didn’t pass. Please review the Sign Off section in the contributing guide to learn more about signing your commit. For this case, you can fix the DCO by running the following commands:

   git rebase HEAD~1 --signoff
   git push -f

2. This commit also needs to be signed with your GPG key. Here’s a helpful resource: Signing Commits.

3. The PR title doesn’t align with the conventional format. There’s a CI check that verifies this, so it’s essential to follow the Conventional Commits standard. I’ve updated the title for you this time but it's jsut FYI for your future contributions 😉

4. Lastly, a more descriptive PR description is preferred. Again, I’ve updated it for you as an FYI for future contributions, so no worries!

@Ritesh-Udgata Ah also another thing could you please kindly make a random comment on the issue #3172 so I can assign the ticket to you?

Done 👍

• Added sign off along with gpg key
• More descriptive PR

Could You please add hacktoberfest accepted label ? Thanks.

@Ritesh-Udgata Hi could you kindly rebase and force pushed the branch? We just added an option which skips the PR Check/Title Checkj CI job if it's from a forked repo.

Could You please add hacktoberfest accepted label ? Thanks.

I've added the labels. Could you tell me if it's missing anything?

Kindly add Hacktober fest accepted label

Kindly add Hacktober fest accepted label

@Ritesh-Udgata I have added all these labels

Are there any other labels you need me to add?

Hello @Ritesh-Udgata, the PR Check/Title Check is still failing. Upon reviewing the workflow file, it appears to be the old version of the YAML file. Please rebase with the remote main branch and force push again to bypass the workflow job.

@Ritesh-Udgata Hmm I still see the old version of the YAML file. I'm looking at your forked repo, the release branch indicates that your branch is 13 commits behind the remote hashgraph:main. Could you please update your branch and push it again?

@Ritesh-Udgata I see you forced push again but seems like your forked repo is still 16 commits behind remote:main.

@Ritesh-Udgata looks like you have updated your forked main branch but didn't update your release. Please run below to update your release:

git checkout release
git rebase main
git push -f

This should update your release branch and should fix the problem.

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

@Ritesh-Udgata Hmm the PR Check CI still fails. Our team is working on an internal fix and will be available soon. Please be patient! I'll keep you posted!

Hello @Ritesh-Udgata so our team just pushed in an internal fix for the PR Check / Title Check CI. Could you please update your forked release branch again to get the latest changes from remote hashgraph:main?

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 59.61%. Comparing base (f540496) to head (441c95e).
Report is 14 commits behind head on main.

❗ There is a different number of reports uploaded between BASE (f540496) and HEAD (441c95e). Click for more details.

HEAD has 4 uploads less than BASE

Flag	BASE (f540496)	HEAD (441c95e)
config-service	1	0
relay	1	0
server	1	0
ws-server	1	0

@@             Coverage Diff             @@
##             main    #3175       +/-   ##
===========================================
- Coverage   82.36%   59.61%   -22.76%     
===========================================
  Files          69       65        -4     
  Lines        4475     4269      -206     
  Branches      881      855       -26     
===========================================
- Hits         3686     2545     -1141     
- Misses        538     1345      +807     
- Partials      251      379      +128