Skip to content

Instantly share code, notes, and snippets.

View cakekindel's full-sized avatar
🍰

Orion Kindel cakekindel

🍰
View GitHub Profile

Id Mapper Api Token Process

Generating

  1. Create a user for the application at https://{env}.id-map.strongmind.com/admin/auth/user/add/
    • The password should be very difficult to guess, and not be saved anywhere.
  2. After creating the user, you should be taken to a view to edit the user
    • (https://{env}.id-map.strongmind.com/admin/auth/user/{usr_id}/change/)
  3. Set the user's email address so that it can be easily identified in dropdowns later
  4. Grant the user the permissions necessary for your Application's API Token
@cakekindel
cakekindel / KEYWORDS_FOR_PRS.md
Last active September 13, 2022 14:47
Pull (Merge) Request Feedback Keywords

Key Words for use in PRs to Indicate Requirement Levels

Intent

This document outlines Key Words borrowed from the IETF RFC #2119, with some minor contextual additions to make them specifically applicable to Pull Requests.

The intent of this document is to provide a common vocabulary for describing the requirement level / "severity" of a Pull Request comment or suggestion.

Contributing to Standards Alignment

  1. Pull and checkout master

  2. Create a feature branch from master

    • If branch represents an Issue or Work Item, the branch should be named the key of the issue / work item, e.g. origin/CROW123
    • If branch is for an out-of-bands change, be sure the name of the branch accurately describes