Eddiebot: fix: role command(wrong desc. for high value role)

[SKULLXL]

The ^roles command contains a field, that is:

• inaccurate(the written content doesn't reflect what one gets after getting the role)
  The problem is with the high-value role description.
  

[github-actions[bot]]

It's great having you contribute to this project

Feel free to raise an Issue! Welcome to the community :nerd_face:

If you would like to continue contributing to open source and would like to do it with an awesome inclusive community, you should join our Discord chat and our GitHub Organisation - we help and encourage each other to contribute to open source little and often 🤓 . Any questions let us know.

[Vyvy-vi]

It would be slightly better if you rename the issue as fix: role command(wrong desc. for high value role)

[AllanRegush]

Change description in config.ts

...
  ROLE: {
    HIGH_VALUE: {
      name: 'high value',
      description:
        'Members with this role have access to more commands to moderate the server (e.g. ban). You get assigned this role if you have a message with +5 reactions',
    },
    BIO: 
...

[ChinmayMhatre]

Is this issue still open . I think the changes have been made right?

[SKULLXL]

I just checked, the changes haven't been made yet. A pull request is needed.

[SKULLXL]

It would be slightly better if you rename the issue as fix: role command(wrong desc. for high value role)

Oh I didn't notice your comment until now, sorry. I renamed the issue now.

[ChinmayMhatre]

just to confirm this is the section in the config.ts to be updated right?

[SKULLXL]

As @AllanRegush pointed out yes this part.

[ChinmayMhatre]

I am new to the server , could you give me a brief of the role , so I could frame the description ?

[SKULLXL]

You get assigned the High Value role if you have a message with +5 reactions, This is best description I could get, and it was provided to me by EddieBot .

[ChinmayMhatre]

Yeah I think that works , It also fits in with the format of the other descriptions . Should I create a pr for that ?

[SKULLXL]

Yap sure. First fork the repo, then create a new branch on your fork, then commit your changes to the new branch u created rather then committing directly to the main branch which is develop prolly. (according to @eddiejaoude you should commit it to a new branch) then after u r done with the commit make a PR.

[SKULLXL]

I am also new to this 😁 , sorry if you cant understand me or if I explained wrong 🤓 .

[ChinmayMhatre]

I'll give a shot . Thanks for the help :)

[eddiejaoude]

Amazing team effort! Thank you all, what an amazing community ❤️ !

Fix in this PR https://github.com/EddieJaoudeCommunity/EddieBot/pull/359