Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 22 2019 16:30
    jcchalte commented #567
  • Jan 15 2019 14:44
    Tigraine commented #564
  • Jan 15 2019 13:45
    CZEMacLeod commented #564
  • Jan 15 2019 11:23
    twenzel commented #564
  • Jan 15 2019 09:32
    Tigraine closed #564
  • Jan 15 2019 09:32
    Tigraine commented #564
  • Dec 28 2018 00:28
  • Dec 19 2018 18:19
    petersmm commented #548
  • Nov 27 2018 08:07

    twenzel on master

    Fix typo in description (compare)

  • Nov 26 2018 11:27

    twenzel on master

    Updated Nuget key (compare)

  • Nov 23 2018 15:38
  • Nov 16 2018 16:56
    rcollette commented #283
  • Nov 12 2018 20:00
    CZEMacLeod commented #283
  • Nov 10 2018 05:12
    rcollette closed #283
  • Nov 04 2018 08:28
  • Oct 30 2018 20:30
    petersmm commented #548
  • Oct 30 2018 20:30
    petersmm commented #548
  • Oct 30 2018 07:56
    twirpx opened #567
  • Oct 24 2018 21:09
    twenzel commented #524
Toni Wenzel
@twenzel

GitHub organization webhook URL

Configure webhook with the following URL for your GitHub organization to notify AppVeyor about team membership changes:

https://ci.appveyor.com/api/github-org/webhook?id=xy

Lauri Kotilainen
@rytmis
I don't think that's it, though, because I added that team to Appveyor yesterday -- if you were already a member, it should have worked.
Maybe it's best if someone creates a new Appveyor account altogether? :)
Toni Wenzel
@twenzel
@rytmis @Tigraine Can I release the current master as version 1.6.0? or is this 1.5.3?
Daniel Hoelbling-Inzko
@Tigraine
If it contains any feature changes i'd do a 1.6.0
And I'd say .NET standard support would qualify as a feature :)
Lauri Kotilainen
@rytmis
Have you checked for API breakage?
If it breaks existing APIs (even by way of package splits), the correct SemVer thing to do would be to bump to 2.0
Daniel Hoelbling-Inzko
@Tigraine
Right
Lauri Kotilainen
@rytmis
Mind you, I'm just stating my opinion -- I'm just another contributor. :)
Not an authority by any means
Daniel Hoelbling-Inzko
@Tigraine
@twenzel @rytmis did any of you release 1.6.0 today?
Just got the email and didn’t see any activity on GitHub so I thought best to ask here if this was intended :)
Toni Wenzel
@twenzel
Yes I did
Daniel Hoelbling-Inzko
@Tigraine
Awesome thanks @twenzel!
Just wanted to make sure nobody got a hold of some of our credentials and is distributing malware :)
Think we should create a tag for the release in GitHub
Toni Wenzel
@twenzel
@Tigraine Tag was created.
mijofr
@mijofr
Hi, which version of LESS featureset does dotless implement?
Lauri Kotilainen
@rytmis
@BellerophonM IIRC the last version that dotless tracked exactly was something like 1.3. After that, most but not all of the language features have been implemented.
/shrug
mijofr
@mijofr
@media block with unrecognised format on line 2143:
[2143]: @media (min-width: (@mode-phone-max-width + 1px)) {
should it be failing to evaluate calculations like this? lessc handles fine, but...
mijofr
@mijofr
(@mode-phone-max-width is in px)
Toni Wenzel
@twenzel
@rytmis should we start a new initiative to get feature par with less.js?
Maybe we could Start with version 2 or should we try version 3?
Lauri Kotilainen
@rytmis
If you have the energy, sure. I can’t lead an effort like that now. Although I did start that project for a formal grammar -based parser...
@BellerophonM obviously it shouldn’t fail like that.
Chirayu Brahmbhatt
@sitecorerebelhub
Hello
Anyone here?
I have query on dotless