Skip to content

Trigger various cache affecting calls asyncronously #65

@JoshuaTheMiller

Description

@JoshuaTheMiller

Many calls are cached for two reasons:

  1. To mitigate bumping into the GitHub API rate limit
  2. To make this application feel "snappier" since some calls can be very time consuming for larger orgs.

This isn't necessarily a v1 requirement, but certain calls (i.e., listing members of an org) NEED to be ran in the background on some set cadence (even when this hooks into GitHub events- we need to validate at some point that no event was missed, after all).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions