Merge branch 'master' into ai-code-format

pull/5423/head
Liana Husikyan 2 months ago committed by GitHub
commit a0fcd1a01b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
  1. 4
      CONTRIBUTING.md
  2. 2
      libs/remix-ui/panel/src/lib/dragbar/dragbar.css
  3. 2
      team-best-practices.md

@ -5,7 +5,7 @@ Everyone is very welcome to contribute on the codebase of Remix. Please join our
## Development
Remix libraries work closely with [Remix IDE](https://remix.ethereum.org). Each library has a readme to explain its application.
When you add a code in any library, please ensure you add related unit tests.
When you add code in any library, please ensure you add related unit tests.
## Coding style
@ -27,7 +27,7 @@ Then you can replace the string with a intl component. The `id` prop will be the
+ <FormattedMessage id="home.learn" />
</label>
```
In some cases, jsx maybe not be acceptable, you can use `intl.formatMessage` .
In some cases, jsx may not be acceptable, you can use `intl.formatMessage` .
```jsx
<input
ref={searchInputRef}

@ -7,7 +7,7 @@
left: 0px;
top: 0px;
height: 0.3em;
z-index: 1000;
z-index: 100;
}
.overlay {

@ -120,7 +120,7 @@ Before starting coding, we should ensure all devs / contributors are aware of:
- A milestone should **only** contain items we are sure to finish.
- The end of a milestone triggers a new release.
- Milestone items and duration should take in account time spent in bugs fixing and support.
- Milestone items and duration should take into account time spent in bugs fixing and support.
- The team should commit to the milestone duration.
- If a dev finish early he/she can help others to push remaining tasks.
- If a dev finish early he/she can work on specifying / integrating the next milestone.

Loading…
Cancel
Save