diff options
| author | Hao Liu <44379968+TheRealHaoLiu@users.noreply.github.com> | 2024-08-22 19:48:56 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-08-22 19:48:56 +0200 |
| commit | 78f345c48694628d36b62728512898f326b6c9f4 (patch) | |
| tree | 9def676edb9468ae3250fe34e255352e3a769c23 /CONTRIBUTING.md | |
| parent | fix: avoid calling undefined method for anonymous users (#15440) (diff) | |
| download | awx-78f345c48694628d36b62728512898f326b6c9f4.tar.xz awx-78f345c48694628d36b62728512898f326b6c9f4.zip | |
Remove old UI (#15414)
* Remove source code for old UI
* Rename ui-next to ui
* Remove license scan for javascript dependencies
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index bae4cefb41..f63d7b7f29 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -126,7 +126,7 @@ If it has someone assigned to it then that person is the person responsible for > If you work in a part of the codebase that is going through active development, your changes may be rejected, or you may be asked to `rebase`. A good idea before starting work is to have a discussion with us in the `#ansible-awx` channel on irc.libera.chat, or on the [mailing list](https://groups.google.com/forum/#!forum/awx-project). -> If you're planning to develop features or fixes for the UI, please review the [UI Developer doc](./awx/ui/README.md). +> If you're planning to develop features or fixes for the UI, please review the [UI Developer doc](https://github.com/ansible/ansible-ui/blob/main/CONTRIBUTING.md). ### Translations @@ -143,10 +143,8 @@ Here are a few things you can do to help the visibility of your change, and incr - No issues when running linters/code checkers - Python: black: `(container)/awx_devel$ make black` - - Javascript: `(container)/awx_devel$ make ui-lint` - No issues from unit tests - Python: py.test: `(container)/awx_devel$ make test` - - JavaScript: `(container)/awx_devel$ make ui-test` - Write tests for new functionality, update/add tests for bug fixes - Make the smallest change possible - Write good commit messages. See [How to write a Git commit message](https://chris.beams.io/posts/git-commit/). |