Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #39760 Get Rid of Flaming Parrot in CI service
    Actions
    Infos
    #39760
    Marie Ange Garnier (marieange)
    2025-10-23 11:50
    2024-10-08 17:01
    41464
    Details
    Get Rid of Flaming Parrot in CI service

    part of doc #1643

    Burning parrot has been introduced in 2016, it can be used everywhere.

    This artifact is dumb, it only lists remaining usages, if we want to replace Flaming Parrot by Burning Parrot we should check with our Design team if it's possible or if they need to rework page UI/UX.

    • Add job

    • Job list

    • Edit job

    Empty
    Empty
    Empty
    • [ ] enhancement
    • [x] internal improvement
    Empty
    Stage
    Empty
    Closed
    2025-10-23
    Attachments
    Empty
    References
    Referencing request #39760

    Git commit

    tuleap/tuleap/stable

    chore: Convert CI to BurningParrot b865db8d2b
    User avatar Nicolas Terray (nterray) , 2025-10-23 10:29
    fix: Make sure repository name is escaped in CI form db52331b18
    User avatar Thomas Gerbet (tgerbet) , 2025-10-23 17:00
    Display settings

    Follow-ups

    User avatar
    Joris MASSON (jmasson)2025-10-21 10:16
    • Summary
      -Get Rid of Flamming Parrot in CI service 
      +Get Rid of Flaming Parrot in CI service 
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Kevin Traini (ktraini)2025-03-28 10:16
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes