All of lore.kernel.org
 help / color / mirror / Atom feed
From: talhacali@gmail.com
To: yocto@lists.yoctoproject.org
Subject: Re: create-layers-setup Yaml support #bitbake
Date: Tue, 11 Apr 2023 07:31:27 -0700	[thread overview]
Message-ID: <28742.1681223487079543700@lists.yoctoproject.org> (raw)
In-Reply-To: <CANNYZj_ga--eO9pUFMw_YTkiULoN9JiDWpRkpXjsHToVxoFw5Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 984 bytes --]

So, how a renovate bot ( https://github.com/renovatebot/renovate ) works is that it parses the files for a specific regular expression that we determine and checks *the line after* this regular expression. So it needs to be in the same json file.

For example:

> 
> {
> "sources": {
> "poky": {
> "git-remote": {
> "branch": "master",
> "describe": "4.2_M2-676-gdf3ce81ed3",
> "remotes": {
> "origin": {
> "uri": "https://github.com/yoctoproject/poky.git"
> }
> },
> // renovate: datasource=git-tags depName=yoctoproject/poky
> lookupName=https://github.com/yoctoproject/poky.git
> "rev": "df3ce81ed3e5491b084041c5bcbd16dada129cf9"
> },
> "path": "poky"
> }
> },
> "version": "1.0"
> }
> 
> 

So, for this file, renovate bot will find the line in red beginning with "// renovate: ", and then check the next line which is "rev": "df3ce81ed3e5491b084041c5bcbd16dada129cf9", if that commit is not the latest commit, then it will replace it with the latest.

[-- Attachment #2: Type: text/html, Size: 4819 bytes --]

  reply	other threads:[~2023-04-11 14:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 13:01 create-layers-setup Yaml support #bitbake talhacali
2023-04-11 14:01 ` [yocto] " Alexander Kanavin
2023-04-11 14:31   ` talhacali [this message]
2023-04-11 14:47     ` Alexander Kanavin
2023-04-11 14:49       ` Alexander Kanavin
2023-04-12 11:12         ` talhacali
2023-04-12 11:34           ` [yocto] " Alexander Kanavin
2023-04-12 16:18             ` talhacali
2023-04-12 16:19               ` talhacali

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=28742.1681223487079543700@lists.yoctoproject.org \
    --to=talhacali@gmail.com \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.