Overview

Once support for user files was added, I realized that people might use files
of mentions rather than flat usernames. This issue is to enhance the user file
support to strip @ from the mention for use.

Haven't begun to debug yet, just opening the issue first

$ ./gh-montage -d hyperledger

+ getopts a:dfhm:p-: OPT
+ shift 1
+ '[' -z hyperledger ']'
+ [[ hyperledger == *\/* ]]
+ ORGANIZATION=hyperledger
+ '[' -z '' ']'
+ MONTAGEFILE=hyperledger-48.jpg
+ test -f hyperledger-48.jpg
++ mktemp -d -t gh-montage
mktemp: too few X's in template ‘gh-montage’
+ TMPDIR=

Noticed you've used -f twice

force | f)
        FORCE=true
        ;;

montage-file | f)
        MONTAGEFILE="${OPTARG}.jpg"
        ;;

Instead of the white background generated in montages today, these images should be transparent, which is more aesthetically pleasing in various use cases.

This will result in changing the resulting image from JPG to PNG.

Token storage change in latest release of gh

This is a message from the GitHub CLI team, maintainers of gh, writing to inform you that the most recent release of gh contains changes which may affect your extension. The latest release introduces the feature of storing authentication tokens in the system keyring (encrypted storage) instead of in a plain text file.
The keyrings that are supported are:

• Keychain on macOS

• GNOME Keyring on Linux (Secret Service dbus interface)

• Wincred on Windows

This has huge security benefits for the users of our tool and was one of our oldest outstanding issues. Unfortunately this change has the potential to break extensions that rely on utilizing the users authentication token to work.

In order to have continued compatibility with gh there are some actions you, as an extension author, need to take. These actions will depend on the implementation of your extension.

Extensions built in Go using go-gh:

1. Upgrade your go-gh version to v1.2.1, the latest version.

   • This can be done using go get github.com/cli/[email protected]

2. Verify that in your extension retrieval of the user authentication token is done using the auth.TokenForHost function.

   • If you were previously accessing the authentication token using any other method it will no longer work.
   • Automatic resolution of the authentication token when using the API clients will continue to work without changes.

All other extensions:

1. Verify that in your extension retrieval of the user authentication token is done by shelling out to the gh auth token command.

   • If you were previously accessing the authentication token using the gh config get command, reading the configuration file directly, or any other methods it will no longer work.

As of right now storing the authentication token in the system keyring is an opt-in feature, but in the near future it will be required and at that point if the changes above are not made then your extension will be broken for all users. If you have any questions/concerns about this change please feel free to open a discussion in the gh repo.

Thanks,
The GitHub CLI Team

Overview

Depending upon the organization or team used along with the dimensions specified, there might not be enough avatars to fill the montage. By default, montage will fill in the end of the montage with a solid color (white by default), however it would be nice especially for the OCD inclined to have that whitespace randomly distributed throughout.

Acceptance Criteria

• Provide an option to balance the whitespace within the montage
• Provide an option to customize the color of the whitespace

Notes

• Creating solid color images using ImageMagic