Lines Matching full:your
9 Join LVGL's community and leave your footprint in the library!
24 - **Spread the Word**: Share your LVGL experience with friends or on social media to boost its visi…
28 - **Tell your ideas**: If you miss something from LVGL we would love to hear about it in a `GitHub …
51 notification like "Hey, I made some updates to your project. Here are
53 (called fork) of the original project under your account, make some
54 changes there, and notify the original repository about your updates.
58 To add your changes you can edit files online on GitHub and send a new
60 updates in your favorite editor/IDE and use git to publish the changes
68 3. Add your changes to the file.
80 repository to your GitHub account (``https://github.com/<YOUR_NAME>?tab=repositories``)
81 2. Clone your forked repository.
82 3. Add your changes. You can create a *feature branch* from *master* for the updates: ``git checkou…
83 4. Commit and push your changes to the forked ``lvgl`` repository.
84 5. Create a PR on GitHub from the page of your ``lvgl`` repository (``https://github.com/<YOUR_NAME…
85 …clicking the *"New pull request"* button. Don't forget to select the branch where you added your c…
86 6. Set the base branch. It means where you want to merge your update. In the ``lvgl`` repo both the…
89 8. If you need to make more changes, just update your forked ``lvgl`` repo with new commits.
168 your contribution complies with the DCO.
170 If your contribution fulfills the requirements of the DCO no further
179 Your own work
182 The simplest case is when the contribution is solely your own work. In