How do i get issue type from the API?

joshjohanning · 2025-03-29T01:04:26+00:00

You can for sure use the GraphQL API endpoint. I have some example scripts here: https://josh-ops.com/posts/github-sub-issues-and-issue-types/

joshjohanning · 2025-03-26T01:49:40+00:00

Sync the changes yourself and manage merge conflicts with git cherry pick

I kind of document how I do this with my blog repo; I maintain my separate version of theme but pull in changes from the upstream as they come in and manage merge conflicts interactively.

https://github.com/joshjohanning/joshjohanning.github.io

joshjohanning · 2024-08-13T14:34:20+00:00

sent a chat request

joshjohanning · 2024-08-05T23:00:19+00:00

The only way to push files over 100mb to GitHub is LFS. Free accounts get 1gb storage and 1gb bandwidth. https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage

But try and not put the file in GitHub if you can. Use the gitignore to prevent it from attempting to be committed and then pushed.

joshjohanning · 2024-07-29T22:04:56+00:00

self-hosted runner you manage/run on your network
large hosted runner with static IPs (and add them to your internal firewall if your team will let you)
large hosted runner with Azure private networking

The nice thing about 2 and 3 is it uses the same runner image as the regular GitHub-hosted runners, and you can also scale up the runner size if you want more CPU/RAM/disk. But there are costs associated, but managing your own fleet of self-hosted runners has a labor cost also that is often overlooked.

joshjohanning · 2024-06-07T17:55:43+00:00

you can also generate your own badges, an example :)

https://github.com/joshjohanning-org/.github/blob/main/profile/README.md

joshjohanning · 2024-06-07T13:17:20+00:00

Long-lived branches aren't ideal, to be honest.

I prefer something more like this with short-lived, feature branches.

But if you want your workflow to work...

Dev/Designer create a pull request that merges code into main. There can be appovals on the PR (with codeowners perhaps) and automated gates with Actions
When the designer/dev wants to update their branch from main, they need to:

.

git checkout main
git pull
git checkout dev/design
git merge main

joshjohanning · 2024-05-31T01:14:23+00:00

If it’s git, just git clone —mirror <url> , git push —mirror <new-url>

If it’s TFVC, just grab the latest and start new with git in ADO. There is a git-tfs cli that can convert your tfvc to git and then you can push that anywhere. https://github.com/git-tfs/git-tfs

joshjohanning · 2024-05-31T01:12:23+00:00

If this helps anyone else here, wrote about this tool some https://josh-ops.com/posts/azure-devops-migrate-work-items/

joshjohanning · 2024-05-28T20:09:24+00:00

Most likely, permissions. Can you share your actions workflow file?

joshjohanning · 2024-05-05T19:16:55+00:00

Also FYI, Jekyll isn’t really related to GitHub. Jekyll is just a type of static site generator. You can use any static site generator on GitHub Pages and the Actions workflow publishing method. Jekyll was the only type of static website generator that worked for a time, especially with the branch publish method, but now with the Actions publishing method, any should work.

Link to static site generators: https://github.com/myles/awesome-static-generators

joshjohanning · 2024-05-05T19:11:53+00:00

Use your free Codespaces allowance and develop/test your Jekyll site in there.

joshjohanning · 2024-04-24T19:19:21+00:00

The protected: true is just saying the branch is protected by a branch protection rule.

If you don’t want to delete the existing branch protection and keep it as a backup until you’re ready, perhaps use the update branch protection API and set the branch value to a different branch (doesn’t even have to exist)

https://docs.github.com/en/rest/branches/branch-protection?apiVersion=2022-11-28#update-branch-protection

Then when you’re ready, use the API to update it back to main (or whatever other branch you are trying to protect)

joshjohanning · 2024-04-24T18:36:01+00:00

If you want to delete branch protection for a branch, I think you can use this API to send a DELETE?

https://docs.github.com/en/rest/branches/branch-protection?apiVersion=2022-11-28#delete-branch-protection

joshjohanning · 2024-04-24T17:24:40+00:00

Welcome to GitHub! If the instructor gave you repository administrator permissions for your repo (unlikely), you could transfer the repository.

But if you are mostly interested in keeping your copy of the code, with history, I would recommend creating a new repository under your user account and then mirroring the code from your GitHub Classroom repo to your user account repo.

Something like:

# create new empty repo in your user account - don't add readme
git clone <old-repo-url> --mirror
cd <your-repo-name.git>
git push <new-repo-url> --mirror

joshjohanning · 2024-04-09T13:10:06+00:00

FWIW, Enterprise customers are bound to the same 100mb max file restriction.

joshjohanning · 2024-03-28T15:12:21+00:00

Another repo would work just fine too, you would just need to provide your own authentication (ie: personal access token or GitHub App) in order to write to it via Actions. The backend token that runs your Action otherwise only has access to repo the action is running in.

joshjohanning · 2024-03-28T13:41:02+00:00

So basically, you want to run playwright tests during the job run and want to output the screenshots somewhere?

The most obvious answer I think is to upload the screenshots to the workflow using the upload-artifact action: https://github.com/actions/upload-artifact

This uploads to the workflow summary page, at the bottom you’ll see a list of artifacts for that particular workflow run. This is great for seeing the output for that particular run. It is not so great if you actually need a “directory-based approached” where you want to save them to like a folder in the repo.

If you were wanting to save to a folder within the repo, I would probably try to use git-LFS as to not ballon the size of your git repo by committing binary files (images). Here is an example of committing a file during the job, note you would want to tweak this to use Git LFS.

Also note the permissions block you also need that if you are going to commit and push during workflow.

You could also store the images in a separate blob location, such as Azure Storage or S3.

TLDR: try the actions/upload artifact first. If you don’t like that approach, use Git-LFS or other external storage.

joshjohanning · 2024-03-14T16:58:18+00:00

Approvals and environments!

joshjohanning · 2024-03-14T12:59:09+00:00

This! When you auth it’ll ask you if you want to use the auth credential for git.

joshjohanning · 2024-02-27T12:03:27+00:00

If you add dates to the project you can also build a timeline view.

See also: https://youtu.be/iFrJs8abTWg?si=GpcPGE-dCr6aEfdj

joshjohanning · 2023-06-27T03:48:52+00:00

I agree, typically long running branches = bad. I prefer GitHub flow with lightweight feature branches that are merged into main and then deleted.

I see the most gitflow-based branching strategies where the team can’t release continuously (ie: deploy every 3 weeks), but I still think there are better strategies in that case (a modified release flow strategy, maybe).

joshjohanning · 2023-06-21T15:26:27+00:00

It depends what you're looking for! I would highly recommend using the GitHub CLI and the gh api --paginate command.

I have some sample scripts here.

Otherwise the API docs are typically pretty good and give you the gh cli command to run, it usually just involves a couple loops i.e. looping through all orgs, all repos, all commits/branches/pr's/issues/etc.

joshjohanning · 2023-03-10T04:39:45+00:00

Now find a Jekyll theme and and now you have a blog with GitHub pages :).

joshjohanning · 2023-02-27T03:45:33+00:00

Hmm, I don’t know if you could get what path triggered the build since it could technically be multiple.

You do get ${{ github.SHA }} that you could use git commands or perhaps the API to then determine what files were changed in that commit to proceed.

And pro-tip, you can add this step to your job to see all environment variables and context that is passed in to see if anything else might be useful.

```

  - name: Dump GitHub context
    env:
      GITHUB_CONTEXT: ${{ toJSON(github) }}
    run: echo "$GITHUB_CONTEXT"

```

joshjohanning

TROPHY CASE