You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To avoid the need for build servers we could utilizes existing CI systems. Therefore the CI would build the project and a plugin / action would be used to upload the deployment and metadata (with above git data) to lagoss.
build new deployments on push (could be configured by CI config)
different environments
main => prod deployment
PR => preview deployment (require approval for 3rd party PRs)
link commit / PR in UI
connect project to git repo (maybe just to automatically push a CI config)
UI
show commit in UI
author
username
name
avatar
forge provider (github, gitlab, ...)
repo
id
owner
name
commit
link
ref (sha)
date
message
link to CI logs
Environment data
LAGOSS_GIT_PROVIDER The Git Provider the deployment is triggered from. Example: github. LAGOSS_GIT_REPO_SLUG The origin repository the deployment is triggered from. Example: my-site. LAGOSS_GIT_REPO_OWNER The account that owns the repository the deployment is triggered from. Example: acme. LAGOSS_GIT_REPO_ID The ID of the repository the deployment is triggered from. Example: 117716146. LAGOSS_GIT_COMMIT_REF The git branch of the commit the deployment was triggered by. Example: improve-about-page. LAGOSS_GIT_COMMIT_SHA The git SHA of the commit the deployment was triggered by. Example: fa1eade47b73733d6312d5abfad33ce9e4068081. LAGOSS_GIT_COMMIT_MESSAGE The message attached to the commit the deployment was triggered by. Example: Update about page. LAGOSS_GIT_COMMIT_AUTHOR_LOGIN The username attached to the author of the commit that the project was deployed by. Example: johndoe. LAGOSS_GIT_COMMIT_AUTHOR_NAME The name attached to the author of the commit that the project was deployed by. Example: John Doe. LAGOSS_GIT_COMMIT_AUTHOR_AVATAR The url to the authors avatar LAGOSS_GIT_PULL_REQUEST_ID The pull request id the deployment was triggered by. If a deployment is created on a branch before a pull request is made, this value will be an empty string. Example: 23.
The text was updated successfully, but these errors were encountered:
To avoid the need for build servers we could utilizes existing CI systems. Therefore the CI would build the project and a plugin / action would be used to upload the deployment and metadata (with above git data) to lagoss.
UI
Environment data
LAGOSS_GIT_PROVIDER
The Git Provider the deployment is triggered from. Example: github.LAGOSS_GIT_REPO_SLUG
The origin repository the deployment is triggered from. Example: my-site.LAGOSS_GIT_REPO_OWNER
The account that owns the repository the deployment is triggered from. Example: acme.LAGOSS_GIT_REPO_ID
The ID of the repository the deployment is triggered from. Example: 117716146.LAGOSS_GIT_COMMIT_REF
The git branch of the commit the deployment was triggered by. Example: improve-about-page.LAGOSS_GIT_COMMIT_SHA
The git SHA of the commit the deployment was triggered by. Example: fa1eade47b73733d6312d5abfad33ce9e4068081.LAGOSS_GIT_COMMIT_MESSAGE
The message attached to the commit the deployment was triggered by. Example: Update about page.LAGOSS_GIT_COMMIT_AUTHOR_LOGIN
The username attached to the author of the commit that the project was deployed by. Example: johndoe.LAGOSS_GIT_COMMIT_AUTHOR_NAME
The name attached to the author of the commit that the project was deployed by. Example: John Doe.LAGOSS_GIT_COMMIT_AUTHOR_AVATAR
The url to the authors avatarLAGOSS_GIT_PULL_REQUEST_ID
The pull request id the deployment was triggered by. If a deployment is created on a branch before a pull request is made, this value will be an empty string. Example: 23.The text was updated successfully, but these errors were encountered: