Created
January 11, 2019 17:05
-
-
Save sheki/3b78c096abf348e6c38d029d4b28c344 to your computer and use it in GitHub Desktop.
Greenkeeper.issue
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hey | |
Just checking in about this ? | |
On 1/7/19 2:36 PM, Abhishek Kona wrote: | |
> | |
> I just reset greenkeeper | |
> | |
> Here is the patch it generates. I expect it to contain updates to `yarn.lock` at the top level which seems missing. | |
> | |
> I have attached my package.json too. | |
> | |
> | |
> Is there a time that works when we can debug this on chat ? | |
> | |
> | |
> Abhishek | |
> | |
> | |
> | |
> On 1/7/19 1:08 PM, Abhishek Kona wrote: | |
>> | |
>> Hey | |
>> | |
>> I do not see the lockfile update for the root directory. ` update lockfile "yarn.lock"` | |
>> | |
>> Can you check for the same. I have the PR which does not contain the lock file update. | |
>> | |
>> There seems to be another bug where the initial PR did not respect the greenkeeper.json and sent updates to all the `package.json` files in our mono-repo. | |
>> | |
>> | |
>> | |
>> On 1/7/19 5:19 AM, Jan from Greenkeeper wrote: | |
>>> | |
>>> Heya, | |
>>> | |
>>> thanks again for your patience while our team had a well deserved rest. | |
>>> | |
>>> We are happy to confirm that lockfile and yarn.lock commits are happening as expected now. | |
>>> | |
>>> Best | |
>>> Jan | |
>>> — | |
>>> | |
>>> -- | |
>>> Jan Jan from Greenkeeper | |
>>> On Fri, Jan 4, 2019 at 12:48 PM, "Jan Lehnardt" <[email protected]> wrote: | |
>>> | |
>>> Thanks for the compliment! | |
>>> On Fri, Jan 4, 2019 at 12:46 PM, "Abhishek Kona" <[email protected]> wrote: | |
>>> | |
>>> That is a long vacation mate. | |
>>> On Thu, Jan 3, 2019 at 12:57 PM, "Jan Lehnardt" <[email protected]> wrote: | |
>>> | |
>>> Heya, | |
>>> | |
>>> we're on holiday break until the 7th, with a reduced support staff (https://twitter.com/greenkeeperio/status/1075767785144242182). | |
>>> | |
>>> We apologise for any inconvenience. This issue will have our full attention from Monday onwards the latest. | |
>>> | |
>>> Best | |
>>> Jan | |
>>> — | |
>>> Greenkeeper CEO | |
>>> On Thu, Jan 3, 2019 at 12:06 PM, "Abhishek Kona" <[email protected]> wrote: | |
>>> | |
>>> hey its been 21 hours without a response. Whats going on | |
>>> On Wed, Jan 2, 2019 at 02:25 PM, "Operator" <[email protected]> wrote: | |
>>> | |
>>> Greenkeeper will be back tomorrow. | |
>>> | |
>>> You'll be notified here and by email ([email protected]) | |
>>> On Wed, Jan 2, 2019 at 02:25 PM, "Abhishek Kona" <[email protected]> wrote: | |
>>> | |
>>> Hey | |
>>> | |
>>> This has gotten quite annoying. I just reset greenkeeper on our account because it was not updating lockfiles for yarn. | |
>>> | |
>>> The new initial PR greenkeeper created still does not have any changes to the yarn lockfiles. | |
>>> | |
>>> Can you look at what is going wrong? | |
>>> | |
>>> intercom |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment