## Description
As we are have been seeing contributors are adding new cypress tests we
want to execute it using `ci-test-limit`. We need to always make a
change to limited-tests file to run new test now we will trigger
`ci-test-limit` directly to save efforts.
Fyi: we need to revert `limited-tests.txt` after everything looks good
on PR. this step to reduce one step effort from our side
Fixes #`Issue Number`
_or_
Fixes `Issue URL`
> [!WARNING]
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._
## Automation
/ok-to-test tags="@tag.Sanity"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/9804245011>
> Commit: 8384096f415124619b17aac586b4a98ccd3717a5
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=9804245011&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Sanity`
> <hr>Fri, 05 Jul 2024 07:03:52 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
## Description
this is a change in the contribution guideline.
1. it informs external contributors of the best practices.
2. it updates some outdated pieces.
## Automation
/ok-to-test tags=""
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!CAUTION]
> If you modify the content in this section, you are likely to disrupt
the CI result for your PR.
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [x] Yes - probably because this relates to them?
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Documentation**
- Updated contribution guidelines to include:
- Requirement to inform maintainers before working on issues.
- Branch naming conventions.
- Proper PR descriptions and including tests.
- Instructions to tag maintainers when raising a PR and handle requested
changes.
- Emphasis on collaborating with maintainers and reviewers to avoid
rejected contributions.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
Currently, our repository is prone to any dev pushing secrets to the repository by mistake. This can become a major problem very quickly and in the case of services like AWS, an alarm is raised and the key is deactivated causing apps using the key to break.
After this PR is merged, people will need to have [git secrets](https://github.com/awslabs/git-secrets) installed in their systems and have to register the AWS secrets to the repo.
The setup instructions have been mentioned [here](https://www.notion.so/appsmith/Getting-Started-e81ccc35463343b28e09c200cdbe5f42#c3183e8e6e404701920dd288b8506360)
Notes:
1. right now, since we are using the pre-commit hooks using husky, the hooks work when we have done yarn install.
2. Also, the scan only checks the directory we are in while making the change or raising the PR. This is because it uses `git ls-files` to get the list of files to scan.
3. If someone doesn't run `git-secrets --register-aws`, the tests will pass automatically since there is no regex registered with the system to scan against.
Fixes#15042
## Type of change
- New feature (non-breaking change which adds functionality)
## Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have 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
- [ ] New and existing unit tests pass locally with my changes
* Add widget development guide in contribution guidelines
* Add link to the widget development guidelines
* Fix formatting issue w.r.t to indentation and images
* A few more missed fixes
* Embed video and indent arguments correctly:
* Fix relative paths
* Fix indentation in Blueprint view
