-
Notifications
You must be signed in to change notification settings - Fork 109
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
regular update based on user feedback #1188
Conversation
…recipes) based on user feedback: #1169
…+ implementations)
MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅ |
@pgmpablo157321 |
Hey Grigori, if you fill out the MLCommons Subscription Form with admin@cTuning.org as the email address and ctuning as the GitHub ID, our automation system should handle that request and put @ctuning on the CLA list. |
Hi Nathan, |
Hmm, may I did that by accident. I see just one commit with cTuning (also maybe capital T is the problem). I think the easiest is to remove this commit but I need to figure out how to do it - I didn't do that before ;) ... Suggestions are welcome! Thank you! |
Hey Grigori, here are some instructions provided by GPT4: Step 1: Identify the Commit to Remove First, identify the commit SHA (hash) of the commit you wish to remove. You can do this by looking at the commit history on GitHub or using the command line:
Step 2: Rebase the Branch Interactively Next, you’ll want to rebase the branch associated with the PR interactively, starting from a commit before the one you wish to remove. If the commit is relatively recent, you can do something like:
X is the number of commits to include in the rebase. Choose a number that includes the commit you want to remove and earlier commits. Step 3: Drop the Commit In the interactive rebase UI (which will open in your default terminal text editor), you'll see a list of commits from oldest to newest. Each commit will start with the word pick. To remove a commit, change the word pick to drop for the commit you want to remove. Save and close the editor to start the rebase. Step 4: Resolve Any Conflicts If there are conflicts during the rebase, git will stop and allow you to fix them. Once resolved, use git rebase --continue to proceed. Repeat as necessary until the rebase is complete. Step 5: Force Push the Changes After successfully rebasing and removing the unwanted commit, you'll need to update the branch on GitHub. Because you've altered the commit history, a standard push won’t work. You'll need to force push:
Using a New Branch If you prefer to avoid altering the history of the current PR branch directly (for example, if the PR has been extensively reviewed and you don't want to disrupt the existing discussion), you can create a new branch from the current state, remove the commit there, and then merge the new branch into the original PR branch (after removing the commit) and then force push the original branch. |
Thank you @nathanw-mlc . However, eventually, we found a simpler solution (thanks to @arjunsuresh). I added ctuning-admin user and updated the GitHub ID from ctuning to ctuning-admin for the MLCommons CLA and it worked. Normally this should avoid our issues in the future when committed via ctuning. Thanks again for your help! |
No description provided.