#Contributing to intents

1 messages · Page 1 of 1 (latest)

obsidian harbor
#

of course. you have to fork the intents repo, commit a change to it (preferably in a feature branch), then create a pull request (PR) to have the change merged from your fork to the main repo

eager oracle
#

I took some time re-reading the instructions which say "Template sentences need to be contributed to our Intents repository on GitHub" and then there's a link to the Codespaces tutorial, which suggests to fork main, but not the repository. I'm a bit confused 😦

obsidian harbor
#

again, this is a discussion for #devs_voice-archived
the instructions are missing this essential setep, but i will guide you through it. you don't have permissions to contribute directly to the home-assistant/intents repo, so you have to fork it into your own copy. once you do that, you can clone it locally or start a codespace on it, create a feature branch and work your magic. once done, run script/lint and script/test to make sure validations pass, then commit the work to your own branch. you now have a fix, but it needs to be merged back into the main repo (home-assistant/intents).
to do that, you have to create a pull request (="main repo maintainers, please review my change proposal and merge it if you see fit"), which will be reviewed by a language leader. if no modifications are necessary, it will get merged and used in production starting with the next major version (2024.2 at the moment). if not, you will receive requests to change stuff, then you commit to your own branch again (which automatically updates the PR) and everything starts all over again

#

the feature branch is not required, but you can't have more than one PR open at a time unless you use branches. besides, when you re-sync your fork, you don't want merge conflicts, which would happen on the main branch if you work directly on it. they can be fixed, but it's not a pleasant thing to do