handler

type Base struct {
	githubapp.ClientCreator

	Installations githubapp.InstallationsService
	ConfigFetcher *ConfigFetcher
	BaseConfig    *baseapp.HTTPConfig
	PullOpts      *PullEvaluationOptions

	AppName string
}

type CheckRun struct {
	Base
}

type ConfigFetcher struct {
	PolicyPath string
}

type CrossOrgMembershipContext struct {
	// contains filtered or unexported fields
}

type Details struct {
	Base
	Sessions  *scs.Manager
	Templates templatetree.HTMLTree
}

type FetchedConfig struct {
	Owner  string
	Repo   string
	Ref    string
	Path   string
	Config *policy.Config
	Error  error
}

type FilesConfig struct {
	Static    string `yaml:"static"`
	Templates string `yaml:"templates"`
}

type HealthCheck struct {
	Status  string `json:"status"`
	Version string `json:"version"`
}

type Index struct {
	Base

	GithubConfig *githubapp.Config
	Templates    templatetree.HTMLTree
}

type IssueComment struct {
	Base
}

type PullEvaluationOptions struct {
	PolicyPath string `yaml:"policy_path"`

	// StatusCheckContext will be used to create the status context. It will be used in the following
	// pattern: <StatusCheckContext>: <Base Branch Name>
	StatusCheckContext string `yaml:"status_check_context"`

	// PostInsecureStatusChecks enables the sending of a second status using just StatusCheckContext as the context,
	// no templating. This is turned off by default. This is to support legacy workflows that depend on the original
	// context behaviour, and will be removed in 2.0
	PostInsecureStatusChecks bool `yaml:"post_insecure_status_checks"`

	// This field is unused but is left to avoid breaking configuration files:
	// yaml.UnmarshalStrict returns an error for unmapped fields
	//
	// TODO(bkeyes): remove in version 2.0
	Deprecated_AppName string `yaml:"app_name"`
}

type PullRequest struct {
	Base
}

type PullRequestReview struct {
	Base
}

type Status struct {
	Base
}

type ValidateCheck struct {
	Message string `json:"message"`
	Version string `json:"version"`
}