The nice thing about git is that nothing is ever really lost after it is committed. For example, if you did above command and realized you wanted the commit back, you could do:
git reflog
Find the sha number (number on the left column) on the item below the top row (top row should have ’ HEAD~1: updating HEAD’), and do:
Q1. Where are you seeing that your one commit was pushed to master?
Q2. The five integration developers, Brady, Rod, Stephen, Tony and Myself are the only ones who can push changes to master. When a commit gets brought into the master branch, if it wasn’t implemented originally by one of the integration developers, github reports “committed by <someone>” in the description after the “authored by <someoneelse>”.
As an example: https://github.com/openemr/openemr/commit/36e7915d6f05d98d7edf798d5f06f24947116d7f
anilnakkani authored November 06, 2012 bradymiller committed November 06, 2012
No code gets into the master branch without a “manual approval” step by an integration developer.
It is impossible to “do something that I should not have” that will impact the master branch by just issuing command to git/github.
Q3. If you have a change in github you’d like to share. I think it’s best to make an announcement here in the developer’s forum with a link to the commit in github. You can also post in the tracker. Just committing code to your own repository is not sufficient to get it into the master code base.
First thing to do is to clean up your repo a bit. Can you paste the content in the .git/config file here (there shouldn’t be any confidential info in there, but look through it before pasting it here); then can provide some commands to clean up your repo a bit and set some end of line settings. Also, are you using Linux or Windows?
And regarding the e setting, this is considered to be deprecated. It basically means the string will be echoed. So, basically:
echo xl(‘name’);
is the same as:
xl(‘name’,‘e’);
You committed it to your personal local and remote (on github) repos. Note your above link has blankev in the path, since you are using your repo. This is yours and nobody else can use it. Note the official OpenEMR repo is here: http://github.com/openemr/openemr
(and only a few of us have access to modify this repo; it actually gets mirrored from the official OpenEMR repo on Sourceforge).
Delete my GitHub as is and open a new GitHub repository?
Don’t expect major changes, but you might expect some field and labels that are incorrectly used or labeled.
Just experiencing and wnat to explore my knowledge from the book:
PHP, MySQL and Apache
I am using the Wondows option as promoted by GitHub. I still don’t get the commands from Linux versions. I want to do too much and learn tooo little…. Stupid, btut that’s the way I try to solve my OpenEMR problems.
I wouldn’t delete your repo, since you have work in there.
Can you get to a command line at all from the windows version? I’m glad to supply the commands you’ll need to straighten things out a bit. But need the content of your.git/config file (this can be found in the the openemr-1 directory.
Our time is better spent helping you use git/github to submit code (note that we can test/submit code that is in git within minutes whereas manual changes, as above, take much longer).
Hi,
From memory (I installed git/gitbash on windows a long time ago), I think you should have a gitbash shortcut on your desktop. If so, click it and then a command line should open up.
-brady
I would create a new empty directory at this point and change into it. (Not sure if you have a bash shell or a regular command prompt at this point.)
the do:
At this point you have a fresh repository and a new branch to track the changes you want to make. You should always make changes/updates in a branch that is separate from the master.
If everything makes sense, seems to be working at this point, what you can do is copy the referral_template.html file from your other directory into this source file tree.
At this point issue the command
git diff
It should show you what has changed from the original.
If all this makes sense, then the next step would be to explain how to “publish” your changes so the rest of us can see.