I have a private GitHub repo that has been rebased a few times and a Jira ticket that is tracking. GitHub and Jira are linked so the commits are tagged to the Jira ticket.
The issue is that previous rebased commits still show on the Jira ticket. The GitHub history is correct? I’m assuming these are cached somewhere In Jira rather than looking through the reflog? I’ve tried a full sync for the Jura’s GitHub App but the rebased commits still show. Is there a way to remove the links?
Related
AWS informed me of leaked account info in a Github repo. It gave me link to the corresponding commit. That commit seems to only be visible if you have the direct sha. I am trying to identify all the other commits that could also contain leaks.
AWS gave the link: https://github.com/myorg/somerepo/commit/1abcdef and that gives me a very old commit with a banner
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
If I try git show 1abcdef on that repo, it's not found. It really cannot be found in git itself. In fact, there is nothing that old.
If I access the commit through the Github API, it is there:
gh api 'repos/myorg/somerepo/commits/1abcdef
I can see all information about it, including the date in 2017.
So I tried:
gh api 'repos/myorg/somerepo/commits?until=2017-12-31'
But that finds nothing. The Github API doesn't seem to mention anything to look at orphaned commits.
I have obviously rotated all credentials for the compromised (dev) account but how can I find other potential problematic commits? If I cannot find them, how could a hacker do it?
my github commits
If you look at the image, an old commit is currently in use for the github pages, why and what do I have to do to make the latest commit pass checks?
I have been told to try vigilant mode but I don't think thats what the issue is about as all the commits are verified.
I simply took down the github pages for the repo and republished and it checked the latest commit.
This probably sounds weird but I would like to fork someone's repo with all the issues attached to it. I know I can fetch changes from the original(upstream) repo such as added files or changed files but I would like to sync issues from the original repo with my repo.
I tried to sync my fork with the upstream but I see that changes in Issues (upstream) are not reflected in my repo.
If that's not possible directly, is there a workaround?
Update 1: So far, as a workaround I found this tool which allows to clone (not fork) issues to your repo. Functionality is limited, but it works https://github.com/gatewayapps/kamino
Update 2: A few more details to clarify my question. I want to be able to:
Fetch changes regularly from upstream repo.
Edit GitHub issues (create new issues, add comments, label issues, add labels) without affecting upstream repo issues.
Merge upstream issues and my issues/edits.
GitKraken can do this for you out of the box by just cloning the forked repo and selecting GitHub as the issue tracker for the selected repo.
All issues will then appear on the sidebar.
I've deployed an app on Netlify through continuous deployment by linking a single Github repo. I had previously been making commits to the project locally, and my contributions were being tracked for this repo. However, now that I've linked the repo to Netlify, it seems no commits or contributions I make are picked up by Github. The commits can still be seen in the Github repo and commits are updated, but the contributions no longer are tracked despite them working previously.
For some context I've checked the Github help page on contributions:
https://help.github.com/en/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile
And cannot see what rule I've violated; I'm working on this on my own, it's a standalone repo, etc etc. considering they were being tracked before for the same repo, I'm confused as to what has changed now that Netlify has been integrated.
Any help/guidance appreciated
So it had nothing to do with Netlify, but my work Mac did not have me globally installed as the commit author with my email. After that, all previous authors were wrong as being my local computer email.
To get around this I followed this tutorial to replace all previous commits with the correct author: How do I change the author and committer name/email for multiple commits?
Would someone please let me know if there is any way to create link to JIRA tickets in my github commit messages?
You can try and follow "Connect Jira Cloud to GitHub", which allows for GitHub or GitHub Enterprise account to be linked to Jira Software.
Your team gets to see their branches, commit messages and pull requests right in the context of the Jira Software issues they're working on
When a developer makes a commit, they should add a Jira Software issue key to the commit message, like this:
git commit -m "PROJ-123 add a README file to the project."
git push origin <branchname>
Update Oct. 2019, you now can set up an autolink reference and GitHub will automatically create links (to external systems) for you.
See "make Jira links clickable in GitHub" (only for GitHub Pro, Team, and Enterprise plans).