onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →Reference

cap-github-action

A CAP project whose MTA build and Cloud Foundry deploy run as two jobs of one GitHub Actions workflow, with the Cloud Foundry credentials read from repository secrets.

What gets deployed is an ordinary CAP project, a Node.js service module, an approuter, an hdb deployer, xsuaa and a HANA HDI container in mta.yaml; the workflow is the subject, and the repository description reads "GitHub Action demo". The build job installs mbt globally, runs mbt build -p cf and uploads ./mta_archives/github-action_1.0.0.mtar, the name the descriptor's own ID and version make, written out in both jobs rather than derived. The deploy job downloads that artifact and calls the third-party guerric-p/cf-cli-action with deploy ./github-action_1.0.0.mtar -f, taking CF_API, CF_USERNAME, CF_PASSWORD, CF_ORG and CF_SPACE from secrets. It triggers on push and pull request against main and on manual dispatch, sets up Node 18.x and actions/checkout@v3, runs no test step, and passes nothing between the jobs but the archive.

GitHub0 ★

Facts

Last pushLicenceUNLICENSED

Where it sits

Lives in
CAP
Demonstrates
CI/CD pipelinesCAPCI/CD pipelinescapabilityA pipeline that builds, tests and delivers an application each time its source repository changes, with a build log that shows which step failed. [Deployment](capability:deployment) describes getting the build onto its target runtime.DeploymentCAPDeploymentcapabilityGetting an application onto a runtime and keeping it there: build descriptors, deployment topology, service bindings and lifecycle operations. The target runtime determines how the application is packaged and configured.
Flavors
Node.jsfrom its runtime
Runs
Cloud Foundry
Requires
@sap/cds^7@sap/cdsartifactThe peer range, as published.

Who is behind it

Mio YasutakeMio YasutakePersonMaintains this
In the atlas: maintains 47, contributes to 47, wrote 10@miyasutamaintainer

What it declares

Every artifact

Type
Sample
Origin
Independently maintained
Use as
A reference
Runtime
Node.js
Runs on
Cloud Foundry

As a sample

Declared for
^7
Form
does not say

Connections2

Download
cap-github-action connectionscap-github-actionPROVIDES→ demonstrates2demonstrates authoredCI/CD pipelinesdemonstrates authoredDeployment

README

quoted from miyasuta/cap-github-action, read
miyasuta/cap-github-action/README.mdOn GitHub

Getting Started

Welcome to your new project.

It contains these folders and files, following our recommended project layout:

File or FolderPurpose
app/content for UI frontends goes here
db/your domain models and data go here
srv/your service models and code go here
package.jsonproject metadata and configuration
readme.mdthis getting started guide
excerpt, UNLICENSED, read the rest, on GitHub

Details

Sources3
GitHub APIdiscovered here, miyasutachecked
github.com/miyasuta/cap-github-actiontree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesnode
declared for^7
deploymentCloud Foundry
discovered viaGitHub API · miyasuta
first seen in the atlas
ecosystem and domaincap, developer-experience
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:miyasuta-cap-github-action
JSON
/artifacts/miyasuta-cap-github-action.json
MCP
Connecting an agent