Merge main into staging (#109)

* implemented chaoss africa keyword triggered DM

Signed-off-by: Precious Abubakar <preciousdanabubakar@gmail.com>

* fixed chaoss-africa DM bugs

Signed-off-by: Precious Abubakar <preciousdanabubakar@gmail.com>

* create new component-joinChaossAfrica, that sends message to newcomers

Signed-off-by: Chinwendu Enyinna <enyinnapc16127@gmail.com>

* Implemented Feedback Corrections

Signed-off-by: Chinwendu Enyinna <enyinnapc16127@gmail.com>

* fix module import error

Signed-off-by: Precious Abubakar <preciousdanabubakar@gmail.com>

* bug report template

Signed-off-by: Precious Abubakar <preciousdanabubakar@gmail.com>

* bug report edit

Signed-off-by: Precious Abubakar <preciousdanabubakar@gmail.com>

* bug report update

Signed-off-by: Precious Abubakar <preciousdanabubakar@gmail.com>

* feature request template, updated bug report template

Signed-off-by: Precious Abubakar <preciousdanabubakar@gmail.com>

* PR template

Signed-off-by: Precious Abubakar <preciousdanabubakar@gmail.com>

* fixes #42

Signed-off-by: meetagrawal09 <agrawalmeet91@gmail.com>

* Replaced CHAOSS Handbook Old Links with The New Link Signed-off-by: Victoria Udofort victoriaedikan23@gmail.com

Signed-off-by: sloaneee <victoriaedikan23@gmail.com>

* minor(handbook link update)

Signed-off-by: Precious Abubakar <preciousdanabubakar@gmail.com>

* Turned off Outreachy Prompt when status is not true

Signed-off-by: Parth Nanda <parthnanda002@gmail.com>

* Delete CODE_OF_CONDUCT.md

Signed-off-by: Matt Germonprez <germonprez@gmail.com>

* Issue 63: Updating Code of Conduct link to point at https://github.com/chaoss/.github/blob/main/CODE_OF_CONDUCT.md

Signed-off-by: viren-01 <vishwakarmavirendra74@gmail.com>

* Fix: fix broken links by replacing with updated links in actionResponse.js   Signed-off-by: Adeyinka Oresanya adeyinkaoresanya@gmail.com

Signed-off-by: AdeyinkaOresanya <adeyinkaoresanya@gmail.com>

* Chore: replace 'Participate page'  with 'Getting Started page' in actionResponse.js   Signed-off-by: Adeyinka Oresanya adeyinkaoresanya@gmail.com

Signed-off-by: AdeyinkaOresanya <adeyinkaoresanya@gmail.com>

* Fix: fix broken links by replacing with updated links in actionResponse.js   Signed-off-by: Adeyinka Oresanya adeyinkaoresanya@gmail.com

Signed-off-by: AdeyinkaOresanya <adeyinkaoresanya@gmail.com>
Signed-off-by: Omokiti <emamuzoomokiti@gmail.com>

* Chore: replace 'Participate page'  with 'Getting Started page' in actionResponse.js   Signed-off-by: Adeyinka Oresanya adeyinkaoresanya@gmail.com

Signed-off-by: AdeyinkaOresanya <adeyinkaoresanya@gmail.com>
Signed-off-by: Omokiti <emamuzoomokiti@gmail.com>

* feat:Add FAQs

Signed-off-by: Omokiti <emamuzoomokiti@gmail.com>

* feat:Add FAQs item

Signed-off-by: Omokiti <emamuzoomokiti@gmail.com>

* fix:link the newcomers channel on slack

Signed-off-by: Omokiti <emamuzoomokiti@gmail.com>

* [Feature]:Translation Files For French and Portuguese

* Signed-off-by: Busayo Ojo <ojobusayo99@gmail.com>

Updated translation folders

* Signed off by Busayo Ojo ojobusayo99@gmail.com

* Created readme.md file

* Update Readme.md

Signed off by Busayo Ojo ojobusayo99@gmail.com

* Revert "Update Readme.md"

This reverts commit 5131f8f.

* Update CONTRIBUTING.md

* Updated Readme file

Signed-off-by: Busayo Ojo <ojobusayo99@gmail.com>

* set up updates

Signed-off-by: peculiaruc <peculiarumeh02@gmail.com>

set up update

Signed-off-by: peculiaruc <peculiarumeh02@gmail.com>

* Signed-off-by: peculiaruc <peculiarumeh02@gmail.com>

Setup update

Signed-off-by: peculiaruc <peculiarumeh02@gmail.com>

* Set up update

Signed-off-by: peculiaruc <peculiarumeh02@gmail.com>

* Set up update

Signed-off-by: peculiaruc <peculiarumeh02@gmail.com>

update

Signed-off-by: peculiaruc <peculiarumeh02@gmail.com>

* Update SETUP.md

* Updated Community Resources

Signed-off-by: Busayo Ojo <ojobusayo99@gmail.com>

* Merged Community and Technical Resource into one

Signed-off-by: Busayo Ojo <ojobusayo99@gmail.com>

* translating the Portuguese basic information page of Getting Started with Bolt For Javascript

Signed-off-by: Elisa Capololo <elisacapololo2017@gmail.com>

* translating the Introduction to Bolt for JavaScript guide into Portuguese

Signed-off-by: Elisa Capololo <elisacapololo2017@gmail.com>

* translation of the Wiki home page into Portuguese

Signed-off-by: Elisa Capololo <elisacapololo2017@gmail.com>

* translating the contribution guide into Portuguese

Signed-off-by: Elisa Capololo <elisacapololo2017@gmail.com>

* addressing comments for change

Signed-off-by: Elisa Capololo <elisacapololo2017@gmail.com>

* adding changes based on comments

Signed-off-by: Elisa Capololo <elisacapololo2017@gmail.com>

* Contributing to the wiki (#99)

* fixing home issue

Signed-off-by: Elisa Capololo <elisacapololo2017@gmail.com>

* additional content contributing to the wiki

Signed-off-by: Elisa Capololo <elisacapololo2017@gmail.com>

---------

Signed-off-by: Elisa Capololo <elisacapololo2017@gmail.com>

* Update actionResponses.js (#106)

We currently link to an old version of the community handbook, so this PR updates that link. Thanks!

Signed-off-by: Elizabeth Barron <elizabeth@naramore.net>

* fix: update dependencies (#108)

Signed-off-by: Precious Abubakar <preciousdanabubakar@gmail.com>

---------

Signed-off-by: Precious Abubakar <preciousdanabubakar@gmail.com>
Signed-off-by: Chinwendu Enyinna <enyinnapc16127@gmail.com>
Signed-off-by: meetagrawal09 <agrawalmeet91@gmail.com>
Signed-off-by: sloaneee <victoriaedikan23@gmail.com>
Signed-off-by: Parth Nanda <parthnanda002@gmail.com>
Signed-off-by: Matt Germonprez <germonprez@gmail.com>
Signed-off-by: viren-01 <vishwakarmavirendra74@gmail.com>
Signed-off-by: AdeyinkaOresanya <adeyinkaoresanya@gmail.com>
Signed-off-by: Omokiti <emamuzoomokiti@gmail.com>
Signed-off-by: Busayo Ojo <ojobusayo99@gmail.com>
Signed-off-by: peculiaruc <peculiarumeh02@gmail.com>
Signed-off-by: Elisa Capololo <elisacapololo2017@gmail.com>
Signed-off-by: Elizabeth Barron <elizabeth@naramore.net>
Co-authored-by: Iyimide <51176311+mide358@users.noreply.github.com>
Co-authored-by: Chinwendu Enyinna <enyinnapc16127@gmail.com>
Co-authored-by: meetagrawal09 <agrawalmeet91@gmail.com>
Co-authored-by: sloaneee <victoriaedikan23@gmail.com>
Co-authored-by: Parth Nanda <parthnanda002@gmail.com>
Co-authored-by: Matt Germonprez <germonprez@gmail.com>
Co-authored-by: viren-01 <vishwakarmavirendra74@gmail.com>
Co-authored-by: AdeyinkaOresanya <adeyinkaoresanya@gmail.com>
Co-authored-by: Omokiti <emamuzoomokiti@gmail.com>
Co-authored-by: Busayo Ojo <ojobusayo99@gmail.com>
Co-authored-by: peculiaruc <peculiarumeh02@gmail.com>
Co-authored-by: Elisa Capololo <elisacapololo2017@gmail.com>
Co-authored-by: Elisa Capololo <34274087+ElisaCapololo@users.noreply.github.com>
Co-authored-by: Elizabeth Barron <elizabeth@naramore.net>

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -0,0 +1,75 @@
+name: Bug Report
+description: Please file a bug report to help us improve the project
+title: "[Bug]: Short description of the problem"
+labels: ["bug"]
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: eg. email@example.com
+    validations:
+      required: false
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: A clear and concise description of what the bug is.
+      placeholder: Tell us what you see! If applicable, add screenshots to help explain the problem.
+      value: "A bug happened!"
+    validations:
+      required: true
+  - type: textarea
+    id: expected-behavior
+    attributes:
+      label: Expected behavior
+      description: A clear and concise description of what you expected to happen.
+      placeholder: What should happen? / What did you expect?
+    validations:
+      required: true
+  - type: textarea
+    id: os-version
+    attributes:
+      label: Your Environment
+      description: Tell us what operating system you're using, along with the version
+      placeholder: e.g. Windows 10, Ubuntu 18.04, macOS 10.14.6
+    validations:
+      required: true
+  - type: textarea
+    id: bug-reproduction
+    attributes:
+      label: Steps to Reproduce the Behavior
+      description: Please share with us a minimalistic template to reproduce the bug.
+      placeholder: |
+        1. In this environment...
+        2. With this config...
+        3. Run/Click on '....'
+        4. See error
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      render: shell
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context
+      description: Is there anything else you can add about the problem?
+      placeholder: eg. related issues, suggestions on how to fix, links for us to have context, eg. stackoverflow, gitter, etc.
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/chaoss/.github/blob/main/CODE_OF_CONDUCT.md)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/feature.yml

@@ -0,0 +1,55 @@
+name: Feature Request
+description: Suggest an idea for this project
+title: "[Feature]: Short description of the feature"
+labels: ["enhancement"]
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this feature request!
+  - type: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: eg. email@example.com
+    validations:
+      required: false
+  - type: textarea
+    id: problem
+    attributes:
+      label: The Problem
+      description: What problem do you hope to solve with this feature?
+      placeholder: e.g. Our Slack Bot has the feature to send site-wide DMs to all the members of the CHAOSS slack channel. I would love to activate this feature for sending our community survey.
+    validations:
+      required: true
+  - type: textarea
+    id: fix
+    attributes:
+      label: How to Fix It
+      description: What do you think needs to be done to fix this problem?
+      placeholder: e.g. Check the app.js file and go to line 114; there is a DM set up...
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: Add any other context about the feature request here (links, screenshots, text, etc).
+      placeholder: |
+        e.g. Message to add in the line of code:
+        Hello there! We recently launched a community survey to get your feedback...
+  - type: textarea
+    id: path
+    attributes:
+      label: Specific File Path(s) on the Repo to be Modified/Refered to
+      description: Please share the specific file path(s) to be modified/refered to in the codebase.
+      placeholder: |
+        e.g. https://github.com/chaoss/chaoss-slack-bot/blob/main/app.js
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/chaoss/.github/blob/main/CODE_OF_CONDUCT.md)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/pull_request_template.md

@@ -0,0 +1,18 @@
+This PR...
+
+## Changes
+
+-
+
+## Screenshots
+
+(prefer animated gif)
+
+## Checklist
+
+- [ ] tested locally
+- [ ] added new dependencies
+- [ ] updated the docs
+- [ ] added a test
+
+Fixes #

CONTRIBUTING.md

@@ -63,6 +63,20 @@ $ git config --global user.email johndoe@example.com
 
 Any pull requests containing commits that are not signed off will not be eligible for merge until the commits have been signed off.
 
+### How to Fix a Failed DCO Check
+Sometimes, you might forget to sign off your commits. We understand, but your pull request will fail the DCO check, and we will not be able to merge it. If this happens, here is how you can fix it:
+
+- To fix a failed DCO check, go to the pull request page and scroll down to the section that shows the successful and failed checks. It is located just above the new comment text area. 
+
+<img width="1437" alt="Screenshot 2023-10-10 at 1 31 32 PM" src="https://github.com/chaoss/chaoss-slack-bot/assets/71160347/c8dab20a-e6e9-4b17-82ab-4f54f9c7d42c">
+
+- Click on the DCO details, and follow the instructions to fix the problem.
+
+ <img width="1437" alt="Screenshot 2023-10-10 at 1 33 43 PM" src="https://github.com/chaoss/chaoss-slack-bot/assets/71160347/d6c04196-e686-42bd-be77-62bff80ce895">
+
+- You can also follow [this guide](https://www.secondstate.io/articles/dco/) for an alternative approach. 
+
+
 ## Keeping in sync with the Chaoss Slack Bot Repository
 Remember to sync your fork with the main branch regularly. To do this:
 Make sure to be in the root folder of the project and the branch should be master branch and type
@@ -76,6 +90,53 @@ $ git pull upstream master
 $ git push origin master
 ```
 
+# Contributing to the wiki
+## Adding or editing wiki pages
+
+You can add and edit wiki pages directly on GitHub or locally using the command line.
+
+Wikis are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud and GitHub Enterprise Server. For more information, see [GitHub’s plans.](https://docs.github.com/en/get-started/learning-about-github/githubs-plans)
+
+## Adding wiki pages
+1. On GitHub.com, navigate to the main page of the repository.
+2. Under your repository name, click **Wiki**.
+![wiki](https://docs.github.com/assets/cb-50195/mw-1440/images/help/wiki/wiki-menu-link.webp)
+3. In the upper-right corner of the wiki, click **New Page**.
+4. Optionally, to write in a format other than Markdown, use the "Edit mode" dropdown to choose a different format.
+![Edit mode](https://docs.github.com/assets/cb-109300/mw-1440/images/help/wiki/wiki-edit-mode-dropdown.webp)
+5. Use the text editor to add your page's content.
+6. In the "Edit message" field, type a commit message describing the new file you’re adding.
+7. To commit your changes to the wiki, click Save Page.
+
+## Editing wiki pages
+1. On GitHub.com, navigate to the main page of the repository.
+2. Under your repository name, click **Wiki**.
+![wiki](https://docs.github.com/assets/cb-50195/mw-1440/images/help/wiki/wiki-menu-link.webp)
+3. Using the wiki sidebar on the right, navigate to the page you want to change. In the upper-right corner of the page, click **Edit**.
+4. Use the text editor to edit the page's content.
+5. In the "Edit message" field, type a commit message describing the new file you’re adding.
+6. To commit your changes to the wiki, click **Save Page**.
+
+
+## Adding or editing wiki pages locally
+Wikis are part of Git repositories, so you can make changes locally and push them to your repository using a Git workflow.
+
+### Cloning wikis to your computer
+Every wiki provides an easy way to clone its contents down to your computer. Once you've created an initial page on GitHub, you can clone the repository to your computer with the provided URL:
+
+```
+$ git clone https://github.com/chaoss/chaoss-slack-bot.wiki.git 
+# Clones the wiki locally
+```
+Once you have cloned the wiki, you can add new files, edit existing ones, and commit your changes. You and your collaborators can create branches when working on wikis, but only changes pushed to the default branch will be made live and available to your readers.
+
+## About wiki 
+The filename determines the title of your wiki page, and the file extension determines how your wiki content is rendered.
+
+Wikis use our [open-source Markup library](https://github.com/github/markup) to convert the markup, and it determines which converter to use by a file's extension. For example, if you name a file foo.md or foo.markdown, wiki will use the Markdown converter, while a file named foo.textile will use the Textile converter.
+
+Don't use the following characters in your wiki page's titles: ```\ / : * ? " < > |```. Users on certain operating systems won't be able to work with filenames containing these characters. Be sure to write your content using a markup language that matches the extension, or your content won't render properly.
+
 # Community Resources
 ## CHAOSS
 - [Website](https://chaoss.community/)

README.md

@@ -21,4 +21,4 @@ If you're interested in cloning our bot for your Slack workspace, you can follow
 
 ## Contributing
 
-To contribute to CHAOSS Slack bot, please follow the guidelines found in our [CONTRIBUTING.md](https://github.com/chaoss/chaoss-slack-bot/blob/main/CONTRIBUTING.md) and our [Code of Conduct](https://github.com/chaoss/chaoss-slack-bot/blob/main/CODE_OF_CONDUCT.md). We love pull requests! We welcome contributions from everyone, whether it's your 1st or your 100th. If you get stuck, please feel free to [ask for help](https://github.com/chaoss/chaoss-slack-bot/issues/new)!
+To contribute to CHAOSS Slack bot, please follow the guidelines found in our [CONTRIBUTING.md](https://github.com/chaoss/chaoss-slack-bot/blob/main/CONTRIBUTING.md) and our [Code of Conduct](https://github.com/chaoss/.github/blob/main/CODE_OF_CONDUCT.md). We love pull requests! We welcome contributions from everyone, whether it's your 1st or your 100th. If you get stuck, please feel free to [ask for help](https://github.com/chaoss/chaoss-slack-bot/issues/new)!