search

guardian / gibbons

Cleanup monkeys for the CAPI API keys table
0 stars 0 forks source link

Remove unused `sbt-release` plugin #53

Closed rtyley closed 8 months ago

rtyley commented 8 months ago

Although present in the initial commit of this project (ee4465c31efe66bb613d802e3e9a385a8fb46710), I don't think this repo has ever publish Maven artifacts, and so doesn't need the sbt-release plugin?

github-actions[bot] commented 8 months ago

Unit Test Results

5 tests  ±0   5 :heavy_check_mark: ±0   0s :stopwatch: ±0s 2 suites ±0   0 :zzz: ±0  2 files   ±0   0 :x: ±0 

Results for commit 91d3708a. ± Comparison against base commit 300cbf5e.

github-actions[bot] commented 8 months ago

Deploy build 297 of Content Platforms::gibbons to CODE

All deployment options - [Deploy build 297 of `Content Platforms::gibbons` to CODE](https://riffraff.gutools.co.uk/deployment/deployAgain?project=Content+Platforms%3A%3Agibbons&build=297&stage=CODE&updateStrategy=MostlyHarmless&action=deploy) - [Deploy parts of build 297 to CODE by previewing it first](https://riffraff.gutools.co.uk/preview/yaml?project=Content+Platforms%3A%3Agibbons&build=297&stage=CODE&updateStrategy=MostlyHarmless) - [What's on CODE right now?](https://riffraff.gutools.co.uk/deployment/history?projectName=Content+Platforms%3A%3Agibbons&stage=CODE)

From guardian/actions-riff-raff.

rtyley commented 8 months ago

I notice now though that a few files in the repository were marked as executable in commit 15549fd70 – I think I’ll undo those changes, because that doesn’t seem deliberate.

Oh yeah, that looks unintentional!