Merge branch 'feat/add-status-to-records-table' into feat/refresh-rec…

…ord-status-using-context-transactions

.github/ISSUE_TEMPLATE/🆕-feature-request.md

@@ -4,19 +4,16 @@ about: Cool new ideas for the project
 title: "[FEATURE]"
 labels: ''
 assignees: ''
-
 ---
 
-<!--  Ask David for help you to contribute https://calendly.com/argilla-office-hours/30min or feel free to submit a pull request straight away: https://github.com/argilla-io/argilla/pulls If you'd like to discuss your feature request or specific needs with our product team, contact Natalia Elvira in our slack community or book a slot with her: https://calendly.com/natalia-elvira/30min -->
-
 **Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
 
 **Describe the solution you'd like**
-A clear and concise description of what you want to happen.
+<!-- A clear and concise description of what you want to happen. -->
 
 **Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
+<!-- A clear and concise description of any alternative solutions or features you've considered. -->
 
 **Additional context**
-Add any other context or screenshots about the feature request here.
+<!-- Add any other context or screenshots about the feature request here. -->

.github/ISSUE_TEMPLATE/🐞-bug-ui-ux.md

@@ -4,34 +4,33 @@ about: UI or UX bugs and unexpected behavior
 title: "[BUG-UI/UX]"
 labels: ''
 assignees: ''
-
 ---
 
-<!--  Ask David for help you to contribute https://calendly.com/argilla-office-hours/30min or feel free to submit a pull request straight away: https://github.com/argilla-io/argilla/pulls or  -->
-
 **Describe the bug**
-A clear and concise description of what the bug is.
+<!-- A clear and concise description of what the bug is. -->
 
 **To Reproduce**
+<!--
 Steps to reproduce the behavior:
 1. Go to '...'
 2. Click on '....'
 3. Scroll down to '....'
 4. See error
+-->
 
 **Expected behavior**
-A clear and concise description of what you expected to happen.
+<!-- A clear and concise description of what you expected to happen. -->
 
 **Screenshots**
-If applicable, add screenshots to help explain your problem.
+<!-- If applicable, add screenshots to help explain your problem. -->
 
-<!-- Since version 1.16.0 you can use `python -m argilla info` command to easily get the used versions -->
 **Environment (please complete the following information):**
+<!-- Since version 1.16.0 you can use `python -m argilla info` command to easily get the used versions -->
  - OS [e.g. iOS]:
  - Browser [e.g. chrome, safari]:
  - Argilla Version [e.g. 1.0.0]:
  - ElasticSearch Version [e.g. 7.10.2]:
  - Docker Image (optional) [e.g. argilla:v1.0.0]:
 
 **Additional context**
-Add any other context about the problem here.
+<!-- Add any other context about the problem here. -->

.github/ISSUE_TEMPLATE/📚-add-a-documentation-report.md

@@ -4,10 +4,7 @@ about: Have you spotted a typo or mistake in our docs?
 title: "[DOCS]"
 labels: ''
 assignees: ''
-
 ---
 
-<!--  Ask David for help you to contribute https://calendly.com/argilla-office-hours/30min or feel free to submit a pull request straight away: https://github.com/argilla-io/argilla/pulls or  -->
-
 ## Which page or section is this issue related to?
 <!-- Please include the URL and/or source. -->

.github/ISSUE_TEMPLATE/🪲-bug-python-deployment.md

@@ -4,30 +4,29 @@ about: Python or Deployment bugs and unexpected behavior
 title: "[BUG-python/deployment]"
 labels: ''
 assignees: ''
-
 ---
 
-<!--  Ask David for help you to contribute https://calendly.com/argilla-office-hours/30min or feel free to submit a pull request straight away: https://github.com/argilla-io/argilla/pulls or  -->
-
 **Describe the bug**
-A clear and concise description of what the bug is.
+<!-- A clear and concise description of what the bug is. -->
 
 **Stacktrace and Code to create the bug**
+<!--
 ```python
 my_python_code
 ```
 ```bash
 my_bash_code
 ```
+-->
 
 **Expected behavior**
-A clear and concise description of what you expected to happen.
+<!-- A clear and concise description of what you expected to happen. -->
 
-<!-- Since version 1.16.0 you can use `python -m argilla info` command to easily get the used versions -->
 **Environment:**
+<!-- Since version 1.16.0 you can use `python -m argilla info` command to easily get the used versions -->
  - Argilla Version [e.g. 1.0.0]:
  - ElasticSearch Version [e.g. 7.10.2]:
  - Docker Image (optional) [e.g. argilla:v1.0.0]:
 
 **Additional context**
-Add any other context about the problem here.
+<!-- Add any other context about the problem here. -->

.github/pull_request_template.md

@@ -1,46 +1,28 @@
-# Argilla Community Growers
-
-Thanks for your contribution! As part of our Community Growers initiative 🌱, we're donating Justdiggit bunds in your name to reforest sub-Saharan Africa. To claim your Community Growers certificate, please contact David Berenstein in our Slack community or fill in this form https://tally.so/r/n9XrxK once your PR has been merged.
-
-# Pull Request Templates
-
-Please go the the `Preview` tab and select the appropriate sub-template:
-
-* [🐞-bug](?expand=1&template=bug.md)
-* [📚-documentation](?expand=1&template=docs.md)
-* [🆕-features](?expand=1&template=features.md)
-
-# Generic Pull Request Template
-
-Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
+# Pull Request Template
+<!-- Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change. -->
 
 Closes #<issue_number>
 
 **Type of change**
+<!--  Please delete options that are not relevant. Remember to title the PR according to the type of change  -->
 
-(Please delete options that are not relevant. Remember to title the PR according to the type of change)
-
-- [ ] Bug fix (non-breaking change which fixes an issue)
-- [ ] New feature (non-breaking change which adds functionality)
-- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
-- [ ] Refactor (change restructuring the codebase without changing functionality)
-- [ ] Improvement (change adding some improvement to an existing functionality)
-- [ ] Documentation update
+- Bug fix (non-breaking change which fixes an issue)
+- New feature (non-breaking change which adds functionality)
+- Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- Refactor (change restructuring the codebase without changing functionality)
+- Improvement (change adding some improvement to an existing functionality)
+- Documentation update
 
 **How Has This Been Tested**
-
-(Please describe the tests that you ran to verify your changes. And ideally, reference `tests`)
-
-- [ ] Test A
-- [ ] Test B
+<!--  Please add some reference about how your feature has been tested.  -->
 
 **Checklist**
-
-- [ ] I added relevant documentation
-- [ ] follows the style guidelines of this project
-- [ ] I did a self-review of my code
-- [ ] I made corresponding changes to the documentation
-- [ ] My changes generate no new warnings
-- [ ] I have added tests that prove my fix is effective or that my feature works
-- [ ] I filled out [the contributor form](https://tally.so/r/n9XrxK) (see text above)
-- [ ] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)
+<!--  Please go over the list and make sure you've taken everything into account -->
+
+- I added relevant documentation
+- follows the style guidelines of this project
+- I did a self-review of my code
+- I made corresponding changes to the documentation
+- I confirm My changes generate no new warnings
+- I have added tests that prove my fix is effective or that my feature works
+- I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)