Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please add this code block to the Tasmota Berry_Playground - Multi-Way Switching for Relays #30

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

LucidEye
Copy link

@LucidEye LucidEye commented Aug 13, 2023

I think I was finally able to do this right thanks to dkebler's instructions, and a lot of reading docs pages.
Would like to add this code example to the Berry_Playground for others to benefit from.
Thank you!

@dkebler
Copy link
Collaborator

dkebler commented Aug 14, 2023

I haven't looked at the content yet but u have committed your vsc settings.  To remove them requires you delete the .vscode directory, stage the delete and then make another commit and push that.  If u need those try a stash instead of delete. After the push reapply the stash and then add .vscode to gitignore.  Can be done in that git extension.  Alternatively one can manually make sure unwanted stuff is not staged B4 a commit.  GitIgnore of directories and files makes that a no brainier.  Git is super usefull powerful tool. Just takes awhile to grok all the details and how to fix mistakes.  Also I bet there's a vsc setting that automatically ignores .vscode in all git repos

@LucidEye
Copy link
Author

Sorry, but I am completely lost now and getting really frustrated. I can not find how to "stage" my files in VSC and re-commit the repo. Instructions claim I can "just right-click on your files and select "stage" from the menu"... well I am not seeing "stage" anywhere on any menu anywhere in VSC. I have no idea why VSC even included that settings file. All I did was install a spell checker extension and add "Tasmota" to it's dictionary... why would that have created a settings file in the git environment???? Why is this so complicated? All I want to do is simply share a short block of code for other people to use, not waste a week having to learn a whole nother VCS extension that I will probably never use again, I have far more important things I really need to be doing.

@dkebler
Copy link
Collaborator

dkebler commented Aug 15, 2023

I understand. We all have a death of time. Just wanted to encourage you to learn to do your own contribution as that is how open source community works. Maybe later this fall I can edit and add your pr so ill just leave it open

@dkebler
Copy link
Collaborator

dkebler commented Aug 15, 2023

It is worth thinking about all the people who give their mostly unpaid time for all this "free" code like tasmota and folks like the person who helped you with your berry question. I did and that's why I did find the time learn to use git and make a Pr as a way to pay it forward

@3ricj
Copy link

3ricj commented Sep 25, 2024

Why is this so complicated? All I want to do is simply share a short block of code for other people to use, not waste a week having to learn a whole nother VCS extension that I will probably never use again, I have far more important things I really need to be doing.

Yeah, the maintainer is combative, not your fault.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants