Commit 68a48d2
committed
CI: Use merge time for activity check
The activity check of the nightly release pipeline extracts the field
'commit.author.date' from the top commit to decide if commit was added
in the last 24 hours. However, unless PRs are reviewed and merged
within 24 hours this activity check will fail. Using the date of the
merge instead leads to a more robust activity check.
To give a concrete example, here are the top lines of today's commit log:
```
{
"sha": "a14abe3265ae8bd3ce463aefa4645bd376d08e5a",
"node_id": "C_kwDOAWrbKtoAKGExNGFiZTMyNjVhZThiZDNjZTQ2M2FlZmE0NjQ1YmQzNzZkMDhlNWE",
"commit": {
"author": {
"name": "Christoph Müllner",
"email": "[email protected]",
"date": "2024-10-12T22:54:57Z"
},
"committer": {
"name": "Christoph Müllner",
"email": "[email protected]",
"date": "2024-10-16T08:08:11Z"
},
[...]
```
The existing code extracts the following time:
```
$ jq -r '.commit.author.date' commit.json
2024-10-12T22:54:57Z
```
The code change in this PR changes this to the following:
```
$ jq -r '.commit.committer.date' commit.json
2024-10-16T08:08:11Z
```
Signed-off-by: Christoph Müllner <[email protected]>1 parent 935b263 commit 68a48d2
1 file changed
+1
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
16 | 16 | | |
17 | 17 | | |
18 | 18 | | |
19 | | - | |
| 19 | + | |
20 | 20 | | |
21 | 21 | | |
22 | 22 | | |
| |||
0 commit comments