I have added T-Display S3 Long to my own fork. How do I add it to your repo?

[MaxGramser]

Moved from #96, originally opened by @rhannink.

Board

Other / not listed here

Your question

Hello,

I have made a fork of your repo and added (with some help from Codex) a new board to this great software. It is the Lilygo T-Display S3 Long board. I have tested it and it seems to work ok.

Question is now, how do I get this board in your repo. Because only after a few days I am some releases behind. The working version is based on firmware 0.11.

The T-Display S3 long is a 3.4" 640x180 IPS touch screen. and it is perfect for placing under a desk for example to control a motorized desk and all the lights ect. in an office

Gr. Remco

[Flpvoigt]

Nice work — the normal way to contribute this board back is to open a pull request from a branch in your fork.

Because your implementation is based on an older release, I would first replay it on top of the current upstream branch instead of opening the PR directly from the old branch:

git remote add upstream https://github.com/MaxGramser/homeassistant_espscreen.git
git fetch upstream
git switch -c feat/t-display-s3-long upstream/main

Then bring only your board-related commits into that new branch:

git cherry-pick <your-commit-sha>
git push -u origin feat/t-display-s3-long

If the default branch is not main, replace it with the repository's default branch. If you have several commits, you can cherry-pick them in order or use a commit range.

After pushing, open your fork on GitHub and click Contribute → Open pull request. The base should be this repository's current default branch, and the head should be your-fork:feat/t-display-s3-long.

In the PR, it would help to include:

• the exact LilyGO board/model and display resolution;
• which pins and board definition were added;
• photos or a short video of the tested device;
• the firmware version you tested;
• build instructions and any limitations;
• only the board-related changes, without generated files or unrelated formatting.

Starting the feature branch from the latest upstream commit avoids mixing your contribution with the fact that the fork is a few releases behind. If cherry-pick reports conflicts, resolve them on this new branch, build/test again, and then push the resolved version.

[MaxGramser]

This request and its replies have moved to the Tessera wishlist.

Please continue there and upvote the wish if you would use it. Sign in with your GitHub account to vote, reply or add examples. More votes help set priorities, including support for new ESP boards and displays.

The original authors, dates, comments and image links have been preserved. This GitHub thread is kept as an archive. GitHub Issues are now for bugs in existing functionality; closing this thread does not mean the request was rejected or implemented. Its current status is on the website.

---

Got a screen running? Tell others which board you have and what works on the Tessera website. It helps everyone pick a screen that works.

Want me to keep building? Consider supporting monthly or buying me a coffee, much appreciated!